Skip to content
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] Bugfixes for asset tags #20723

Merged
merged 2 commits into from
Mar 26, 2024
Merged

Conversation

clairelin135
Copy link
Contributor

@clairelin135 clairelin135 commented Mar 25, 2024

Fixes a few bugs:

  • Makes filter value display with key: value instead of value: key
  • Removes an extra ! operator to fix filtering
  • Adjusts asset overview page to hide __dagster_no_value tag values
image image

@clairelin135
Copy link
Contributor Author

clairelin135 commented Mar 25, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @clairelin135 and the rest of your teammates on Graphite Graphite

Copy link

github-actions bot commented Mar 25, 2024

Deploy preview for dagit-core-storybook ready!

✅ Preview
https://dagit-core-storybook-jaycga5fg-elementl.vercel.app
https://03-25-claire-fix-filter-by-tag.core-storybook.dagster-docs.io

Built with commit f0d5251.
This pull request is being automatically deployed with vercel-action

@clairelin135 clairelin135 force-pushed the 03-25-claire/fix-filter-by-tag branch from a8f7f18 to a2e3405 Compare March 25, 2024 22:13
@clairelin135 clairelin135 changed the title [ui] Bugfix for filtering by tag [ui] Bugfixes for asset tags Mar 25, 2024
@clairelin135 clairelin135 marked this pull request as ready for review March 25, 2024 22:15
<Tag key={idx}>
{tag.key}={tag.value}
</Tag>
<Tag key={idx}>{buildTagString({key: tag.key, value: tag.value})}</Tag>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

buildTagString(tag) ?

@@ -37,7 +37,7 @@ export const useAssetTagFilter = ({
/>
);
},
getStringValue: ({value, key}) => `${value}: ${key}`,
getStringValue: ({value, key}) => `${key}: ${value}`,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops

@@ -81,6 +81,6 @@ export function doesFilterArrayMatchValueArray<T, V>(
return !filterArray.some(
(filterTag) =>
// If no asset tags match this filter tag return true
!valueArray.find((value) => !isMatch(filterTag, value)),
!valueArray.find((value) => isMatch(filterTag, value)),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this function is used by other filters, can you confirm those still work?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think its only used for owners and tags, this implementation works for both

@clairelin135 clairelin135 force-pushed the 03-25-claire/rename-asset-catalog-overview branch from 9b9c637 to c4d72d8 Compare March 26, 2024 16:10
Base automatically changed from 03-25-claire/rename-asset-catalog-overview to master March 26, 2024 16:20
@clairelin135 clairelin135 force-pushed the 03-25-claire/fix-filter-by-tag branch from a2e3405 to 8cd3fe1 Compare March 26, 2024 16:25
@clairelin135 clairelin135 merged commit a4efae2 into master Mar 26, 2024
2 checks passed
@clairelin135 clairelin135 deleted the 03-25-claire/fix-filter-by-tag branch March 26, 2024 17:28
PedramNavid pushed a commit that referenced this pull request Mar 28, 2024
Fixes a few bugs:

- Makes filter value display with `key: value` instead of `value: key`
- Removes an extra `!` operator to fix filtering
- Adjusts asset overview page to hide `__dagster_no_value` tag values

<img width="1278" alt="image"
src="https://github.com/dagster-io/dagster/assets/29110579/fc15029a-88eb-4978-be01-e50c52f2422b">
<img width="1280" alt="image"
src="https://github.com/dagster-io/dagster/assets/29110579/2aa51cbc-2566-4387-a9f6-2031c4ab7e52">
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants