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

[24.1] Fix display tags in FormSelect when available #18918

Draft
wants to merge 6 commits into
base: release_24.1
Choose a base branch
from

Conversation

davelopez
Copy link
Contributor

Fixes #18667

FixFormSelectorTags

How to test the changes?

(Select all options that apply)

License

  • I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

@davelopez
Copy link
Contributor Author

davelopez commented Oct 1, 2024

Currently, the filtering will not take into account the tags, only the main "label". Did the previous component filter by tag too in the search box?

Edit: I figured out we should filter by tag anyway, people might remember the tag better than the dataset name. So I'll modify the default search to include tags.

@davelopez davelopez marked this pull request as ready for review October 1, 2024 18:06
@github-actions github-actions bot added this to the 24.1 milestone Oct 1, 2024
@ElectronicBlueberry
Copy link
Member

did you do a quick performance test for very large histories?

@davelopez
Copy link
Contributor Author

Nope, if this was available before I just hope it shouldn't be worse than before. 😅

This is loading everything and is not (nor was) using any kind of pagination before I'm afraid.

@ElectronicBlueberry
Copy link
Member

I'm worried mostly about the search, and how responsive it feels while typing. I think we have a filter worker which could be used here in case it's unresponsive.

@davelopez
Copy link
Contributor Author

I think we have a filter worker which could be used here in case it's unresponsive.

Ahh cool! I'm happy to use it then. I'll search for it.

@davelopez davelopez marked this pull request as draft October 2, 2024 16:17
@@ -51,19 +55,22 @@ const emit = defineEmits<{
(e: "input", value: SelectValue | Array<SelectValue>): void;
}>();

const filter = ref("");
const filteredOptions = useFilterObjectArray(props.options, filter, ["label", "value"]);
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@ElectronicBlueberry is this what you had in mind?

Unfortunately, I cannot filter by tags because the filter expects only the keys of the object and in this case, the tags are in the sub-object "value.tags" 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants