In .info files, modules can expose human readable labels. These labels are not cached in the system table, though .info file descriptions are. I would like to see another column, `label`, added to the system table where these can be cached.

I know we try to avoid schema changes and API changes within major versions, but this seems pretty harmless. Moreover, the module_list() function could be the API to this data, by returning a an array of module_name => module_label, instead of module_name => module_name.

I'm happy to write the patch, but I'd like some +1s before I do it to 5.1 instead of HEAD.

-M

Comments

killes@www.drop.org’s picture

I doubt this will be added to D5. Why do you consider it important?

mfredrickson’s picture

I doubt it too, but it never hurts to ask. :-)

As to why this is important, my use case is as follows: I'm writing a module that creates a new hook. When I invoke my hook, I get back a list of functions different modules support. I'd like to group these function by their parent module in a select list opt group. eg:

- User
-- Content Author
-- User Names
-- User Roles
- Organic Groups
-- Group Subscribers
-- Group Administrators
.... etc

Right now, I can only use the module short name (e.g. og instead of Organic Groups) because the long name (while in the info file) is not cached anywhere.

It's too bad I noticed this now, instead of 4 weeks ago. Hopefully, it will be deemed such a minor change that it can still get in.

-M

marcingy’s picture

Version: 5.1 » 8.x-dev

Bumping version

jhedstrom’s picture

Issue summary: View changes
Status: Active » Closed (works as designed)

AFAIK, this has been completely overhauled in 8.x. Feel free to re-open if somebody wants to pursue this.