-
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
[1/k][ui] Pull, display generic kinds in place of compute kind #24159
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @benpankow and the rest of your teammates on Graphite |
Deploy preview for dagit-core-storybook ready! ✅ Preview Built with commit 8637118. |
@@ -10,11 +10,15 @@ export const LEGACY_COMPUTE_KIND_TAG = 'kind'; | |||
export const COMPUTE_KIND_TAG = 'dagster/compute_kind'; | |||
export const STORAGE_KIND_TAG = 'dagster/storage_kind'; | |||
|
|||
export const KIND_TAG_PREFIX = `dagster/kind/`; |
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.
You could define this here: https://github.com/dagster-io/dagster/blob/master/js_modules/dagster-ui/packages/ui-core/src/runs/RunTag.tsx#L7
01672e2
to
c734909
Compare
8dcf5cd
to
6e6b2eb
Compare
Merge activity
|
6e6b2eb
to
8637118
Compare
Summary
Begin moving from compute kinds to kinds by requesting the list of kinds from GraphQL (introduced in #24154, a superset of the compute kind) and then displaying those in place of the compute kind tags in the asset graph and asset list.
Changelog
NOCHANGELOG