Skip to content

[epilogue] Improve support for robot base classes in epilogue#8886

Open
SamCarlberg wants to merge 2 commits into
wpilibsuite:mainfrom
SamCarlberg:epilogue/widen-robot-support
Open

[epilogue] Improve support for robot base classes in epilogue#8886
SamCarlberg wants to merge 2 commits into
wpilibsuite:mainfrom
SamCarlberg:epilogue/widen-robot-support

Conversation

@SamCarlberg
Copy link
Copy Markdown
Member

Generate an update method for any logged Robot class, not just TimedRobot

Continue to generate a bind method for TimedRobot subclasses

Also removes unnecessary import statements for generated loggers, since they're using fully-qualified names in the generated Epilogue class now.

Generate an `update` method for any logged Robot class

Generate a `bind` method for logged TimedRobot subclasses
@SamCarlberg SamCarlberg requested a review from a team as a code owner May 10, 2026 18:15
@SamCarlberg SamCarlberg added the component: epilogue Annotation-based logging library label May 10, 2026
@zachwaffle4
Copy link
Copy Markdown
Contributor

Should the bind method for TimedRobot subclasses also be generated for OpModeRobot subclasses? (And why can't it just be generated for RobotBase subclasses itself?)

@SamCarlberg
Copy link
Copy Markdown
Member Author

Should the bind method for TimedRobot subclasses also be generated for OpModeRobot subclasses? (And why can't it just be generated for RobotBase subclasses itself?)

TimedRobot and OpModeRobot don't have the same signatures; OpModeRobot doesn't accept a phase offset like TimedRobot does.

RobotBase doesn't have an addPeriodic function, so bind wouldn't make sense there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component: epilogue Annotation-based logging library type: testing Related to testing.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants