robot: Reduce prematch status lights code nesting#430
Open
auscompgeek wants to merge 1 commit intomainfrom
Open
robot: Reduce prematch status lights code nesting#430auscompgeek wants to merge 1 commit intomainfrom
auscompgeek wants to merge 1 commit intomainfrom
Conversation
auscompgeek
commented
Jun 24, 2025
| else: | ||
| self.status_lights.rainbow() | ||
| else: | ||
| self.status_lights.no_auto() |
Member
Author
There was a problem hiding this comment.
This adds an additional no_auto call if we somehow have no starting pose. Unless we somehow commit a broken path or path name, this should be impossible. It's probably better to not gaslight the drive team into thinking the vision system is completely broken if it's actually our code though, if we somehow get into this impossible situation.
This file contains hidden or 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
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.
The logic for the prematch status lights is a bit difficult to follow as it's so deeply nested, and not entirely self-documenting.
It's probably much easier to understand if a few of these are written like preconditions. So this splits out all the logic for the preflight status lights into a method named as such, and uses early returns rather than heavy nesting.