-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Extensions should be sorted case insensitive #18808
Labels
area/devtools
Issues/PR related to maven, gradle, platform and cli tooling/plugins
Milestone
Comments
If the extensions are sorted regardless of case, then Camel gPRC will be listed together with the other G extensions, and so on. |
good catch! |
@davsclaus would you provide a PR? |
gastaldi
added
area/devtools
Issues/PR related to maven, gradle, platform and cli tooling/plugins
and removed
triage/needs-triage
labels
Jul 19, 2021
gastaldi
added a commit
to gastaldi/quarkus
that referenced
this issue
Jul 19, 2021
gastaldi
added a commit
to gastaldi/quarkus
that referenced
this issue
Jul 19, 2021
gastaldi
added a commit
to gastaldi/quarkus
that referenced
this issue
Jul 19, 2021
gastaldi
added a commit
to gastaldi/quarkus
that referenced
this issue
Jul 19, 2021
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Jul 21, 2021
Fixes quarkusio#18808 (cherry picked from commit 7038c0f)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
(Describe the problem clearly and concisely.)
Extensions are sorted with case sensitive, eg A..Za..z
Expected behavior
(Describe the expected behavior clearly and concisely.)
They should be sorted regardless of case
Actual behavior
(Describe the actual behavior clearly and concisely.)
To Reproduce
Steps to reproduce the behavior:
Screenshots
(If applicable, add screenshots to help explain your problem.)
See the screenshot
Environment (please complete the following information):
Additional context
(Add any other context about the problem here.)
The text was updated successfully, but these errors were encountered: