mavschema.xsd: add superseded tag #809
Open
Conversation
This file contains 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
hamishwillee
commented
May 4, 2023
| @@ -202,7 +202,16 @@ | |||
| </xs:complexType> | |||
| </xs:element> | |||
|
|
|||
| <xs:element name="deprecated"> | |||
| <xs:element name="wip"> | |||
There was a problem hiding this comment.
FYI, just a reorder for wip and deprecate, which is what makes this a bit messier. Sorry.
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.
This adds a
supersededtag. Once this is in. my intent is to divide the existing deprecated tags into those that are actually deprecated by the standard (and we hope to remove) and those that are just superseded by a new message, command, enum that we hope one day everyone will upgrade too.The difference being that superseded is as much a hint to autopilots as users that there is something that might we worth upgrading to.
This is a precondition to any kind of release process.
NOTE. I thought about adding deprecated, wip, superseded as possibilities for field values and param values. However I'm not sure this is useful. I.e. In one way it is - you can indicate that things are new - or not intended to be used with clear tagging. But you can't actually "remove" a field that is in common.xml if you add "deprecated" and you can add WIP but it's public ... so not sure. Assuming not for now.