-
Notifications
You must be signed in to change notification settings - Fork 29.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
Expand PickList to support *grouping* #11468
Comments
This comment has been minimized.
This comment has been minimized.
Would the team consider a PR for this API enhancement request so QuickPickItems can be grouped? |
@gjsjohnmurray Lets first discuss the API change. Would you just surface what we use internally? There we allow the items list to be either a QuickPickItem or a QuickPickSeparator which then separates the groups and can have a label. |
@chrmarti that makes good sense to me. @alefragnani is that what you wanted? |
@gjsjohnmurray I never thought the API would be that way. I was thinking about a group/category data attached to each But, if the proposed API ( I just wonder how/if I should deal with the ordering, visibility and counting myself when the user filters the PickList, with the I didn't dig in VS Code source to see how the internal API works today, but with the right documentation and samples, I guess it wouldn't be a problem. Thank you |
The built-in filtering removes all separators because it also sorts across groups by the best match. |
Big 👍 for that |
We would copy the group labels across items. If the group label were alternating A, B, A, we would have two options: either sort them by first appearance or consider it distinct groups. I like an approach without the replication and ambiguities better. |
Indeed thanks @gjsjohnmurray. /duplicate #74967 |
Originally reported in #7019 (comment)
The idea is to show items in the pick list, just like Go to Symbol, where you have some kind of groups of items (that appears when you type '@:' in the pick list)?
Thanks in advance
The text was updated successfully, but these errors were encountered: