-
Notifications
You must be signed in to change notification settings - Fork 57
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
WIP: Schema backwards compatibility #272
Merged
Merged
Changes from all commits
Commits
Show all changes
30 commits
Select commit
Hold shift + click to select a range
277ef1c
Intermediate commit: add unit test for older schema
drdavella 55845f9
Minor refactor of debug code for _get_yaml_content
drdavella c5e9e37
Add new wcs unit test for backwards compatible schema conversion
drdavella 49a37d6
Do not allow old versions of schemas w/o explicit implementation
drdavella 8246d69
First pass at backwards compatibilty for tag class...
drdavella ed491b5
Fix handling of obsgeovel and obsgeoloc in tag v1.0.0
drdavella 604ed9a
Add unit test for GCRS frame backwards compatibility...
drdavella 3d6c272
Add unit test for using tags that are not defined...
drdavella 611ca8d
Add unit test for tag implementation newer than schema read...
drdavella a2e370a
Restore previous logic for warning for schema version mismatch...
drdavella 2d2632e
Custom tag class in unit test shouldn't inherit AsdfType...
drdavella 44d0261
Update tag unit test to check for expected warnings
drdavella 5d85aef
WIP to handle tag classes with unsupported schema versions
drdavella cadb129
WIP: moved version compat logic into yamlutils...
drdavella 8ae634a
Modify extension type hierarchy to diffentiate custom classes...
drdavella 242c41c
Extension classes now have `supported_version` field...
drdavella e269f41
Remove xfail for "test_newer_tag"
drdavella bb39b80
Update documentation to reflect AsdfType-->UserType
drdavella cbc3b76
Fix __init__.py to reflect AsdfType-->UserType
drdavella 2d49117
Break CelestialFrame tests in to prompt more updates
drdavella ab4aac3
Prototype of way to have multiple versions in one tag class...
drdavella d0b49ee
Remove xfails from wcs tests
drdavella 6c91c4a
supported_versions attribute now only supports list and set
drdavella ba62a14
Add documentation for supported versions attribute
drdavella e1d90f3
Remove extraneous and misleading code from unit test
drdavella 60cd2f5
Refactor the check for schema version compatibility
drdavella 37b1037
Add unit test for supported_versions for UserType
drdavella a3a7ad4
Refactor to handle versioned tag classes in ExtensionList creation...
drdavella 2b90d9e
Supported version unit test now passes. Minor changes
drdavella a813f6c
Rename UserType->CustomType
drdavella File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
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.
Is it possible to indicate a range of versions supported? I suspect this may be a common case and it would be more painful to have to explicitly list each version that is supported. Also, it may be good to outline version synchronization issues within the library. I.e., is it possible that schemas get updated versions before the library is updated to deal with them? If so, what happens? Is there a way to indicate that we presume that the library supports future versions without out listing them explicitly (e.g., perhaps indicating a range of version where the end range is indefinite). By default the behavior may be that it tries to handle these newer versions and warns that it failed. I wonder if we have considered all the timing issues, but I may be all wet.
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.
The idea of supporting version ranges occurred to me as well, and I think it's probably the right thing to do. I also think it makes sense to address it in a separate issue after getting this PR merged.
Likewise, I think it makes sense to allow for indefinite ranges. None of this should be too difficult to support; it will just require some modifications to the way these things are represented internally. Again, I'd like to make a separate PR for these.
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 agree it should be in a different PR