-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[FEATURE_REQUEST] Allow case insensitive alphabetical sorting #352
Comments
Hiya @BOZG - Thanks for your suggestion :) |
This issue has been marked as a good first issue for first-time contributors to implement! This is a great way to support the project, while also improving your skills, you'll also be credited as a contributor once your PR is merged. If you're new to web development, here are a collection of resources to help you get started. You can also find step-by-step tutorials for common tasks within Dashy, on the Dev Guides page. If you need any support at all, feel free to reach out via GitHub Discussions.
|
I can make this change either later this evening, or tomorrow. Unless anyone else would like to pick it up, this should be a pretty easy task to implement, sorting is done within the Section component: dashy/src/components/LinkItems/Section.vue Lines 196 to 199 in 2032481
So using sortAlphabetically(items) {
return items.sort((a, b) => (a.title.toLowerCase() > b.title.toLowerCase() ? 1 : -1));
}, The reverse-alphabetical sort uses the same method, and then just reverses the order, so the change is only needed in one place. |
Implemented in #354 :) |
Is your feature request related to a problem? If so, please describe.
Choosing "alphabetical" as the "Sort by" option is case sensitive meaning that 'A' and 'a' are not sorted together.
Describe the solution you'd like
If feasible, an option to ignore case sensitivity when sorting alphabetically would be nice. Just making sorting case insensitive doesn't strike me as an alternative as I'm sure there are others out there who prefer sorting as it is.
This is obviously a very personal peeve and easily mitigated by me renaming services so I don't expect it to be a priority in any way.
Priority
Low (Nice-to-have)
Is this something you would be keen to implement
No response
The text was updated successfully, but these errors were encountered: