-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Examples should migrate from robotInit #120
Comments
I'm not sure this is a great idea at the moment. The robot constructor does a bunch of things, and I think that it depends To support this, we would need to ensure that the robot constructor is empty or does things that doesn't matter. It looks like |
Fixes wpilibsuite#2679 Supersedes wpilibsuite#2689 Does not touch RobotBuilder docs, as those are generated and need to be updated by regenerating the code Does not touch Python. robotpy/examples#120
Fixes wpilibsuite#2679 Supersedes wpilibsuite#2689 Does not touch RobotBuilder docs, as those are generated and need to be updated by regenerating the code Does not touch stacktraces article, as the code and stacktraces need to be updated together Does not touch Python. robotpy/examples#120
* Change usage of robotInit to Robot Constructor Fixes #2679 Supersedes #2689 Does not touch RobotBuilder docs, as those are generated and need to be updated by regenerating the code Does not touch stacktraces article, as the code and stacktraces need to be updated together Does not touch Python. robotpy/examples#120 * Remove bad Override * Remove additional reference
I thought the conclusion was RobotPy keeping robotInit was fine: wpilibsuite/allwpilib#6623 (comment) |
Problem description
wpilibsuite/allwpilib#6623 removed uses of robotInit in the WPILib examples and changed to using the robot constructor. This is to prepare for eventual deprecation robotInit. Python examples should be similarly updated.
Operating System
RoboRIO
Installed Python Packages
No response
Reproducible example code
No response
The text was updated successfully, but these errors were encountered: