Repository navigation
Align UART/GPS period fields - #223
Merged
Merged
Conversation
Member
Author
lorennorman
approved these changes
Oct 12, 2026
lorennorman
left a comment
lorennorman
left a comment
Member
There was a problem hiding this comment.
oh yeah no brainer, great catch. i should've noticed this when i updated all the periods recently.
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 following
periodfields inuart.protoandgps.proto(which inherits fromuart.proto) are in millseconds. The rest of theperiodfields across the API are in seconds.This PR aligns the comments here, I'll check out two corresponding issues to fix alignment in the codebases.