Add a SbpMsgUnknown type in for the sbp_msg_type_t enum [POS-559] #1105
Conversation
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
lkloh
changed the title
silverjam
reviewed
Mar 31, 2022
|
@woodfell or @RReichert any concerns with this? |
silverjam
approved these changes
Apr 1, 2022
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.
Description
@swift-nav/devinfra
Add a
SbpMsgUnknowntype to thesbp_msg_type_tenum for C++ messages so we have a way to initialize messages of undetermined type. This was first suggested here.API compatibility
Does this change introduce a API compatibility risk?
No, this adds a message enum option but does not subtract or change anything already in use.
JIRA Reference
https://swift-nav.atlassian.net/browse/POS-559