Order component names alphabetically

The order is curated by the project maintainers, with the drag & drop in the Issues vertical tab of project's edit screen. I'm tempted to move this to the core queue, and the maintainers can order however wanted.

I agree. This is for the people who can access node/3060/edit to solve. Moving to a better queue.

Thanks,
-Derek

Cleaning up issues tagged with version 10 erroneously after the recent update, and found this ... so just checking if 10.0.x-dev was chosen intentionally here? :-)

@ressa: Thanks for the asking. The version for this issue is totally irrelevant. It has nothing to do with the Drupal source code in Git. It's about the Drupal core project page itself.

Also, setting to RTBC, since there's nothing for the community to review / test. It's just something someone with edit permissions to the project node has to do. We can't supply a patch or make this any easier for them. They just have to do it if they want to. ;)

Cheers,
-Derek

Great, just checking in. Also, adding my own issue about this as well.

RTBC++++ Please and thank you. :)

sqlite driver is listed before 'database update system', but I would assume that was intentional when it was added, due to it being a subcomponent of 'database system'.

I think this is a duplicate of #2864277: Make the Component list searchable (or easier to choose from) and #2660144: [Plan] Update core components tbh. If there are components that are simply out of order then it's fine to re-order those, but removing the fake-subcomponent thing we have now needs more discussion.

#2797899: Alphabetize core components select list was a child of #2660144: [Plan] Update core components, but I marked it duplicate with this (since this is the older issue). Adding that as a parent here. I think this is a distinct part of that plan, not a duplicate.

I should be able run a query to alphabetize these, if we do want to go ahead with this. I just want to get sign-off from core maintainers before doing that.

@drumm That would be great. Hope this gets approved.

I don't think an automated alphabetize query is the right solution. Honestly, I'm not really in favor of this as-is. Sorry for RTBC'ing before. :(

We currently "group" the components:
- Core systems
-- sometimes subsystems -- e.g. all the DB drivers are right under the main "database system" component).
- Core modules
- A few FE misc things "markup, CSS, etc"
- Core themes
- Truly misc components

I don't think we should move "MySQL driver" after between menu* and node.module, it should be "next to" the "database system". Re-reading, that's basically what @catch said in #7.

Maybe we need support for opt groups for core's components, and then alphabetize within each official grouping?

Probably better discussed at the parent issue, but it's also weird that we have 'menu system' vs. 'menu.module', etc. That doesn't make any sense, and I can't imagine anyone (subsystem maintainers included) can understand the difference.

Also, while the distinction between field.module vs. field_ui.module or views.module vs. views_ui.module makes sense for the organization of the code (so you can disable the UI parts but leave the rest of the functionality enabled), that distinction basically makes no sense for issue components. Anyone who's tending to the views_ui "queue" is undoubtably tending to the views "queue" as well. We seem to have consolidated "node.module" into "node system" a while ago. We should do the same with "menu*" (just call all of it "menu system"), "field*" => "field system", "views*" => "views system", etc. Such a consolidation would probably shave 10-15 separate choices out of the list, which would be a step in the right direction.

1 thing that'd help the DB drivers... instead of calling them "mysql db driver" if we called them "database mysql driver" then we could alphabetize everything and it'd all work. ;)

Especially if we also renamed "database system" to something like "database core system". ;)

Ditto with all the themes... if we call them "theme: Bartik", "theme: Claro" etc, then actual alphabetizing would make more sense.

Looks like this is a can of worms. :) However it's solved it would be amazing to easily find what you are looking for. I suppose autocomplete isn't an option but I would be happy to start typing "layo" and it would show me the components with "layo" in the text. I have no idea how much the component dropdown is used though so maybe this isn't a big deal to most people even if I struggle to find things.

Yeah the current setup is a component/subcomponent setup, even if its not evident. I agree simply alphabetising them would be a mistake.

Based on the last comment this seems like a won't fix is that correct?

Closing as works as designed based on #14. If someone disagrees please reopen explaining why.