-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
server: metadata separation: reorganize metadata types #6103
Conversation
Deploy preview for hasura-docs ready! Built with commit 9ce7e15 |
-> Remove traces of multi source related types -> Use ordered hashmaps and hashsets in 'Metadata' type
9ce7e15
to
7401802
Compare
@@ -72,86 +72,12 @@ runClearMetadata _ = do | |||
buildSchemaCacheStrict | |||
return successMsg | |||
|
|||
applyQP1 |
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 logic this function does has been moved to parseJSON
of the Metadata
type. See parseListAsMap
function.
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.
LGTM
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.
LGTM, only a few nits.
Description
This is an incremental PR towards #5797. It refactors metadata types that will be used to incrementally modify the metadata.
It also adds a big type class inThis change will be made in subsequent incremental PR.Hasura.Class
that will be used as a general interface for providing a metadata API. We may want to discuss this type class in some more detail, to decide whether it follows a design pattern we'd like to include in our code base, or if it needs further thought.Although this PR adds types that can hold new metadata, the intention is that it does not change what metadata actually gets stored. Any new style metadata code included should not be used. However, we should check this carefully.
Changelog
CHANGELOG.md
is updated with user-facing content relevant to this PR. If no changelog is required, then add theno-changelog-required
label.Affected components
Related Issues
Solution and Design
Steps to test and verify
Limitations, known bugs & workarounds
Server checklist
Catalog upgrade
Does this PR change Hasura Catalog version?
Metadata
Does this PR add a new Metadata feature?
GraphQL
Breaking changes