-
Notifications
You must be signed in to change notification settings - Fork 68
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
Return package sorted by pacakge title #647
Comments
Currently the packages are sorted by the package name: https://github.com/elastic/package-registry/blob/master/search.go#L172 I think what you are looking for is to sort it by package title? Example here of the Big IP Package:
|
Yes, exactly package title. I don't see values in using name. |
@mtojek is it something still relevant? |
I suggest to review titles and package names first. In the example you brought: Package name: f5 Shouldn't it be consistent to have "F5 Big-IP..."? If you're used to package names (e.g. f5), you will look for it at the right place in the alphabet. I understand that it might be misleading if you are browsing packages ordered by titles. Anyway it shouldn't be a complex adjustment in the source code (let me see if I can prepare a quick fix). |
I do agree that name and titles should be consistent! Sorting by title is not a viable option I think. What if I am looking for F5? Should I scroll down until "Big-IP ..."? That's weird also. What do you think? |
In this particular case (F5) I agree with you, but I'm not convinced in the other case: log vs "Custom logs". That's the reason why we may need to adjust ordering. |
Originally created by @mostlyjason on elastic/kibana#74577
Currently, the list of integrations shown in Ingest Manager is not alphabetically sorted. This makes it more difficult to find integrations as the number grows from 39 and higher. You can see in the screenshot below that Big IP comes after the letter C. Also custom logs, is after the letter 'K'. It seems like there some kind of sort, but its not sorted based on the name displayed on the screen.
The text was updated successfully, but these errors were encountered: