[x] Code is complete, and naming of variables, methods and classes are readable by non-coder humans.
[ ] This code change has been tested and validated working as expected.
[ ] This code change has been reflected in robot documentation in the docs folder.
[x] The questions below have all been answered.
[x] The title of this PR has been updated to describe the change made, for example, [Subsystem or Command Name] Short description of change.
[x] Assignees (usually yourself) have been assigned in the "Assignees" section to the right.
[x] Relevant reviewers have been assigned under the "Reviewers" section at the right.
What is changing and why?
In our discussions on 3/5, we determined that we will need to track some basic robot state to implement needed commands to support driving. These state values are:
whether or not we are in endgame
the current targeted scoring position, if any
the state of the claw
This PR implements a new class RobotState that tracks the first two, and adds the third as a method on the Claw subsystem.
How was this tested?
Nothing here changes operation of the robot yet, so there's no need to do an on-robot test of this code.
Is there anything the reviewer of this PR needs to know to validate that this code is correct?
What do your team members need to know about this?
Had to override and push the merge through -- i was last commit doing a cleanup of merge from main. Lots of whitespace fixes made RobotContainer merge be confused.
Related Issues and PRs
Issue:
Related PRs:
Checklist
docs
folder.[Subsystem or Command Name] Short description of change
.What is changing and why?
In our discussions on 3/5, we determined that we will need to track some basic robot state to implement needed commands to support driving. These state values are:
This PR implements a new class
RobotState
that tracks the first two, and adds the third as a method on theClaw
subsystem.How was this tested?
Nothing here changes operation of the robot yet, so there's no need to do an on-robot test of this code.
Is there anything the reviewer of this PR needs to know to validate that this code is correct?
What do your team members need to know about this?