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

Multiselectors handle comma-separated lists badly #1974

Open
teceler opened this issue Feb 8, 2024 · 1 comment
Open

Multiselectors handle comma-separated lists badly #1974

teceler opened this issue Feb 8, 2024 · 1 comment

Comments

@teceler
Copy link
Collaborator

teceler commented Feb 8, 2024

You'd think, since we display things like tags and access lists as comma separated lists, that pasting them into the multiselect would work. no. it treats it as one tag/username/etc.

Fixing this would probably need to handle the possibility of a comma in a username or tag but if we're displaying them that way we should think about that anyway.

@Throne3d Throne3d changed the title Multiselectors handle comma-seperated lists badly Multiselectors handle comma-separated lists badly Feb 13, 2024
@Throne3d
Copy link
Contributor

Looks like the comma tokenizer stuff only works on freeform entries: https://select2.org/tagging#automatic-tokenization-into-tags

I tried adding tokenSeparators: [','], to the configuration but it ignored it for the user entries. Maybe there's some way to hook into the paste event and handle that specifically, or some other event for the input search field for select2?

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

No branches or pull requests

2 participants