Skip to content

Case insensitive sorting for subscriptions list #4961

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

Open
pamelafox opened this issue Mar 18, 2025 · 4 comments · May be fixed by #4969
Open

Case insensitive sorting for subscriptions list #4961

pamelafox opened this issue Mar 18, 2025 · 4 comments · May be fixed by #4969

Comments

@pamelafox
Copy link
Member

It looks like the subscriptions list are ASCII-sorted, but then some developers dont realize their subscriptions are actually lowercased. Could it do some normalization of the casing before it sorts the subscriptions?

@crazy4pi314
Copy link

That would be super helpful, also if it needs to keep subscriptions for different tenants together, having a heading indicating that would also be nice :)

@weikanglim
Copy link
Contributor

keep subscriptions for different tenants together, having a heading indicating that would also be nice

This totally makes sense as a suggestion! I don't think we'll be able to get to this soon due to how the UI prompt works.

I hope this isn't too much an inconvenience. I know it can affect the usability of discovering the right subscription to use for the first time. For myself, when I do know the subscription name, I generally type the name directly and avoid scrolling the list entirely.

@weikanglim
Copy link
Contributor

Submitted #4969 after some brief testing -- the case-insensitive sorting does look much more presentable!

@JeffreyCA
Copy link
Contributor

Should we do this for other pickers like the resource group picker?

The portal seems to default to that as well:
image

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 a pull request may close this issue.

4 participants