-
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] Replace compute kind, storage kind filters + tags with generic kind #23805
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 de5fd89. |
eee4bd6
to
dc901b6
Compare
954290e
to
20f596c
Compare
93eab68
to
c8e8f0e
Compare
20f596c
to
0221c00
Compare
c8e8f0e
to
841f271
Compare
0221c00
to
c513640
Compare
841f271
to
4621a59
Compare
c513640
to
a5ba3ac
Compare
4621a59
to
15ba582
Compare
a5ba3ac
to
34df0c8
Compare
15ba582
to
fac926c
Compare
34df0c8
to
79e7389
Compare
.filter((o) => o) | ||
.flatMap((a) => a as string[]), | ||
), | ||
).sort(), |
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.
I think you can just do this:
Array.from(
new Set(assets.map((a) => a?.definition?.kinds || []).flat())
).sort(...);
Also, it's generally good to use this to ensure a reliable string sort:
.sort((a, b) => COMMON_COLLATOR.compare(a, b))
fac926c
to
2ce7807
Compare
79e7389
to
8a98eb6
Compare
2ce7807
to
77fc7ec
Compare
8a98eb6
to
a80d4e0
Compare
77fc7ec
to
08ee3e9
Compare
a80d4e0
to
dd71cda
Compare
08ee3e9
to
96207b3
Compare
dd71cda
to
d0c68c4
Compare
96207b3
to
1e9e28c
Compare
d0c68c4
to
c6c941a
Compare
1e9e28c
to
455f2e8
Compare
c6c941a
to
dfe241f
Compare
455f2e8
to
02120fb
Compare
dfe241f
to
35f0eb4
Compare
02120fb
to
e074331
Compare
35f0eb4
to
166d0fd
Compare
e074331
to
403be73
Compare
56e97bc
to
5382818
Compare
5382818
to
de5fd89
Compare
## Summary Re-implementation of #23805 which is slightly lighter weight (but still touches a lot of surface area). Substitutes in the notion of a generic kind filter rather than specifically compute kind. ## Test Plan Existing unit tests, local dagit. ## Changelog `NOCHANGELOG`
Summary
As we move to 'kind' being a first class notion, with multiple potential values, this PR tears out the compute kind and storage kind filters and UI components and drops in a singular 'kind' replacement, backed by the
kinds
GQL endpoint.Test Plan
Tested locally, few new unit tests.