This repository was archived by the owner on Mar 28, 2025. It is now read-only.
Draft
Conversation
| } | ||
| }, | ||
| swerve)) | ||
| .finallyDo(swerve::finishTrailblazerRequest) |
Contributor
There was a problem hiding this comment.
what if we want to do accurate things with trailblazer and don't want it to end within some threshold
Member
Author
There was a problem hiding this comment.
set shouldEnd to false and it will continuously maintain the end position
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
TODO: Need to figure out how to not constantly go back into
TELEOPswerve state when thenormalDriveRequest()gets triggered from robot state transitions. I guess maybe that's not an issue since Trailblazer is callingswerve.startTrailblazerRequest()continuously?