Right now, the system.module configuration object holds a single enabled key with the module - weight pairs under it. There seems to be no point in not having the module-weight pairs on top. May I get a reasoning for why this is done or better just move them to the top?

Comments

elvis2’s picture

elvis2 CreditAttribution: elvis2 commented

@sun, can we close this since there has been no response in 33 weeks?

cweagans’s picture

cweagans
He/Him
Primary language English
Location Boise, ID, USA
CreditAttribution: cweagans commented

We don't just close issues that don't have responses.

sun’s picture

sun
Primary language German
Location Karlsruhe
CreditAttribution: sun commented
Issue summary: View changes
Status: Active » Closed (works as designed)

There are two reasons for using an 'enabled' parent key:

  1. Consistency: system.module and system.theme should work in the same way.
  2. Extensibility: Like system.theme, it is always possible that we need to add further keys to system.module.
chx’s picture

chx CreditAttribution: chx commented

Note this issue is moot because everything is now in core.extension.