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.
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
add basic implementation for Shoulder code #23
add basic implementation for Shoulder code #23
Changes from 3 commits
050d0de
9bffd1b
a18d7b9
ad57f69
16c8d55
667deb6
5bace98
0ec76d8
af526e9
236444c
7361037
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
here the ControlType should be kSmartMotion I believe if you want to use the other fancy things
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks Max! agreed - we'll switch to that if/when we use it, tho keeping it at position since we're just setting P, I, D, and FF for now. we don't need the rest yet, at least for the initial version. (we ended up not needing it (at least in the time we had before CC) for the other mechanisms.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see aa8bd25 for the history with the other mechanisms if you're curious.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. All looks good then, have fun fighting Jay('s linter).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Yeah, it's the various whitespace checks. I'll adhere to them for now, tho I actually disagree with some of them (they make code a bit harder to read), so I might make some edits to our checkstyle.xml.
When I get a chance, I'll also see if we can switch to a client-side linter (with github side checks as well), so we can check/automatically reformat code as part of the authoring process, vs the submission process. eg https://docs.wpilib.org/en/stable/docs/software/advanced-gradlerio/code-formatting.html.