-
Notifications
You must be signed in to change notification settings - Fork 97
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 description for constellation identifier to bounds messages [OC-1087] #1407
Conversation
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!
rust/sbp/src/link.rs
Outdated
@@ -351,6 +351,7 @@ mod tests { | |||
assert_eq!(*count.borrow(), 1); | |||
} | |||
|
|||
#[allow(dead_code)] |
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.
@pcrumley What do you think of this change I had to make in order to have CI pass? See https://snav.slack.com/archives/C05HP6S1D2Q/p1711097571216779 for more context
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.
Hey @IsakTjernberg I was on PTO and just getting back into the swing of things. I think it makes more sense to fix the lints like this #1408 because #[allow(dead_code)] is kind of broad lint.
remove change to allow dead code because no longer required
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.
We ended up taking a different fix to get around this clippy lint issue
Quality Gate passed for 'libsbp-c'Issues Measures |
Thanks @pcrumley! |
Description
Add description for what the constellation identifier means in the orbit&clock bounds, code&phase biases bounds, orbit&clock bounds degradations messages.
API compatibility
Does this change introduce a API compatibility risk?
No, it's just adding clarifying documentation to the SBP spec.
JIRA Reference
https://swift-nav.atlassian.net/browse/OC-1087