[WIP] Schema version priority for union dataclass comparison #2959
+151
−149
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.
Tracking issue
flyteorg/flyte#5489
Why are the changes needed?
Since we plan to primarily support newer versions of JSON schemas in the future, we would like to update the JSON schema version priority in the
literal
metadata field.What changes were proposed in this pull request?
dict
while generating attribute list ingenerate_attribute_list_from_dataclass_json_mixin
function.How was this patch tested?
Setup process
Screenshots
Check all the applicable boxes
Related PRs
#2932
#2859
Docs link
None