-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Adding Domain to Glossary Terms #6135
Adding Domain to Glossary Terms #6135
Conversation
…ahub into domain-to-glossary
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.
things are looking good! the last thing you'll need is to query for the domain on the frontend. So in src/graphql/glossaryTerm
under the getGlossaryTerm
query, you'll need to get:
domain {
...entityDomain
}
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.
@@ -35,6 +37,7 @@ export const Preview = ({ | |||
typeIcon={entityRegistry.getIcon(EntityType.GlossaryTerm, 14, IconStyleType.ACCENT)} | |||
deprecation={deprecation} | |||
parentNodes={parentNodes} | |||
glossaryAssociatedDomain={domain} |
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.
can you just reuse the existing domain
prop on DefaultPreviewCard
instead of creating a new glossaryAssociatedDomain
prop?
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.
nice!
Checklist