The aim of the Pull Request is to update the metadata.get_standard_metadata to 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 as singer-discover to choose fields.
Manual QA steps
Check that you're happy with the testing and implementation
Risks
I have not supported the anyOf key 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.
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