Feature/get nested metadata #133
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 of change
This PR relies on #132
The aim of the Pull Request is to update the
metadata.get_standard_metadatato provide metadata entries for nested fields. Without this feature if a user wants to disable a nested field they are able to but must manually add the metadata entry to the catalog. This would provide the entry by default allowing for my easy use of tools such assinger-discoverto choose fields.Manual QA steps
Risks
anyOfkey in the schemas. I'm not sure how this would work anyway as having schemas with variable types doesn't seem terribly useful for data management purposes.Rollback steps