-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[ui] Try to appease GraphQL backcompat test #25304
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @hellendag and the rest of your teammates on Graphite |
Deploy preview for dagit-core-storybook ready! ✅ Preview Built with commit 8634d8e. |
739ed32
to
051dabb
Compare
051dabb
to
8634d8e
Compare
import {MetadataEntryFragment} from './types/MetadataEntryFragment.types'; | ||
import { | ||
MetadataEntryFragment, | ||
TableMetadataEntryFragment, |
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.
Importing the fragment instead of the TableMetadataEntry
type allows us to avoid types that aren't included in the fragment.
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.
aha
## Summary & Motivation Update imports to try to fix backcompat error. ## How I Tested These Changes Buildkite
Summary & Motivation
Update imports to try to fix backcompat error.
How I Tested These Changes
Buildkite