2024 beta #62
Merged
2024 beta #62
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update 2024-beta branch --------- Co-authored-by: Cole MacPhail <[email protected]>
# Description Support for the Logitech F310 controller has been added Fixes #6 ## Type of change - [X] New feature (non-breaking change which adds functionality) # How Has This Been Tested? - All axes and buttons used in the old `LogitechF310` were checked against the values used internally by WPILib's `CommandXboxController` to ensure they matched. This should prevent triggers from being bound to the wrong key. # Checklist: - [ ] My code follows the style guidelines of this project - [X] I have performed a self-review of my code - [X] I have commented my code, particularly in hard-to-understand areas - [X] I have made corresponding changes to the documentation, if any - [X] My changes generate no new warnings - [X] I have performed tests that prove my fix is effective or that my feature works, if necessary - [ ] New and existing unit tests pass locally with my changes --------- Co-authored-by: IanTapply22 <[email protected]> Co-authored-by: Cole MacPhail <[email protected]>
Sync beta branch with main --------- Co-authored-by: Cole MacPhail <[email protected]> Co-authored-by: github-actions <>
Updated 2024-beta branch to be synced with main --------- Co-authored-by: Cole MacPhail <[email protected]>
# Description This pull request adds an example subsystem for students to use to learn about how subsystems and commands are used in a robot environment. Fixes #18 ## Type of change Please delete options that are not relevant. - [X] New feature (non-breaking change which adds functionality) # Checklist: - [x] My code follows the style guidelines of this project - [X] I have performed a self-review of my code - [X] I have commented my code, particularly in hard-to-understand areas - [X] I have made corresponding changes to the documentation, if any - [X] My changes generate no new warnings - [ ] I have performed tests that prove my fix is effective or that my feature works, if necessary - [ ] New and existing unit tests pass locally with my changes --------- Co-authored-by: Ian Tapply <[email protected]> Co-authored-by: Cole MacPhail <[email protected]>
# Description This pull request adds support for addressable LEDs. It also allows you to create LEDs with multiple segments so you can set the mode of each segment to your desire and allows you to seamlessly add your own custom LED modes. Fixes #28 ## Type of change Please delete options that are not relevant. - [x] New feature (non-breaking change which adds functionality) - [x] This change requires a documentation update # How Has This Been Tested? So far it hasn't, right now this will stay as a draft PR until tested further # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation, if any - [x] My changes generate no new warnings - [ ] I have performed tests that prove my fix is effective or that my feature works, if necessary - [ ] New and existing unit tests pass locally with my changes --------- Co-authored-by: github-actions <> Co-authored-by: Cole MacPhail <[email protected]>
# Description Updated `2024-beta` branch with main ## Type of change - [x] New feature (non-breaking change which adds functionality) # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation, if any - [x] My changes generate no new warnings - [x] I have performed tests that prove my fix is effective or that my feature works, if necessary - [x] New and existing unit tests pass locally with my changes --------- Co-authored-by: Cole MacPhail <[email protected]> Co-authored-by: github-actions <>
# Description Created a vision subsystem that can be used for the drive odometry, tracking our position on the field, or for tracking game objects. Fixes #36 ## Type of change Please delete options that are not relevant. - [x] New feature (non-breaking change which adds functionality) # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation, if any - [x] My changes generate no new warnings - [x] I have performed tests that prove my fix is effective or that my feature works, if necessary - [x] New and existing unit tests pass locally with my changes --------- Co-authored-by: github-actions <>
Updated the `2024-beta` branch to be synced with the `main` branch --------- Co-authored-by: Cole MacPhail <[email protected]>
# Description - Updated the drive-related dependencies to the latest beta - Updated drive telemetry to the new CTRE suggested way - Created a new drive subsystem and deleted the old one Fixes #8 ## Type of change - [x] New feature (non-breaking change which adds functionality) # How Has This Been Tested? N/A # Checklist: - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation, if any - [ ] My changes generate no new warnings - [ ] I have performed tests that prove my fix is effective or that my feature works, if necessary - [ ] New and existing unit tests pass locally with my changes --------- Co-authored-by: github-actions <>
# Description Renamed IntakeGamepieces enum to IntakeGamepiece to make more sense grammatically Fixes #54 ## Type of change Please delete options that are not relevant. - [x] Bug fix (non-breaking change which fixes an issue) # How Has This Been Tested? N/A # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation, if any - [x] My changes generate no new warnings - [x] I have performed tests that prove my fix is effective or that my feature works, if necessary - [x] New and existing unit tests pass locally with my changes --------- Co-authored-by: github-actions <>
# Description Moved the scoring states for the intake to separate classes to improve organization and to remove the large conditional block Fixes #51 ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) # How Has This Been Tested? N/A # Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation, if any - [x] My changes generate no new warnings - [x] I have performed tests that prove my fix is effective or that my feature works, if necessary - [x] New and existing unit tests pass locally with my changes --------- Co-authored-by: github-actions <> Co-authored-by: kaleb-dodd <[email protected]>
# Description This pull request adds the intake subsystem to the robot container, allowing the intake to be used. Scoring states have also been updated to be publicly accessible Fixes #53 ## Type of change Please delete options that are not relevant. - [X] New feature (non-breaking change which adds functionality) # Checklist: - [X] My code follows the style guidelines of this project - [X] I have performed a self-review of my code - [ ] I have commented my code, particularly in hard-to-understand areas - [X] I have made corresponding changes to the documentation, if any - [X] My changes generate no new warnings - [X] I have performed tests that prove my fix is effective or that my feature works, if necessary - [X] New and existing unit tests pass locally with my changes --------- Co-authored-by: github-actions <>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Merge of WIP code into main
Breaking change (fix or feature that would cause existing functionality to not work as expected)
My code follows the style guidelines of this project
I have performed a self-review of my code
I have commented my code, particularly in hard-to-understand areas
I have made corresponding changes to the documentation, if any
My changes generate no new warnings
I have performed tests that prove my fix is effective or that my feature works, if necessary
New and existing unit tests pass locally with my changes