-
Notifications
You must be signed in to change notification settings - Fork 57
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
Order better the Collections info dropdown #567
Comments
Hi i would like to resolve the issue , so can you help me on how can i replicate the situation. |
Hi @Krrish-29 - that would be great! Firstly, you need to check out and run Phoenix locally: Secondly, navigate to the ATLAS example, and open the collections tab: This popup is the "collections info overlay": In |
hello, I would like to work on this issue, How exactly do you want it sorted, alphabetically or by type? |
By type is more important than alphabetical (but my by type first, then
alphabetical?)
…On Fri, 13 Dec 2024 at 14:04, Pratham ***@***.***> wrote:
hello, I would like to work on this issue, How exactly do you want it
sorted, alphabetically or by type?
—
Reply to this email directly, view it on GitHub
<#567 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABTTQSJ2F3SQMUJTTDGDS632FLLPJAVCNFSM6AAAAABRP6WCJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBRGQZDCMRVHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
ok i will start working on it |
Can you help me understand what the different types are? |
See this comment:
|
Hi @EdwardMoyse can I get an update on this? |
Sorry, yes that is exactly what I was thinking of! |
When we open the Collections Info windows, the collections dropdown is currently unsorted. See below.
What would be ideal is to divide it into different types of collections. Or we add another dropdown to select the type, with this dropdown then only showing collections of the requested type.
If all of this is too hard (or as a stopgap) we should at least sort it alphabetically.
The text was updated successfully, but these errors were encountered: