I wonder...

So _advanced_help_parse_ini() is where a lot of this comes down to, and seems to rely on drupal_get_path() to retrieve the module path.

I've kinda got this dream of pulling in the readme and/or advanced_help from every branch of every project that's being parsed to create documentation for the API module, rather than just generating advanced_help for modules that are installed.

This would be handy to use alongside, for example, the views, ctools or panels advanced help. The help provides a lot of key documentation and would be nice to reference alongside topics and all the other documentation issues.

How would you go about tackling this issue? Would this be a patch? Is this out of the scope of advanced_help? Should I 'fork' advanced_help and bring it into the api module somehow so that api module can parse advanced_help on it's own, possibly requiring advanced_help and using some of it's higher level functions while replacing some of the lower level ones?

Comments

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
CreditAttribution: gisle commented
Status: Active » Closed (won't fix)

Yes, this is out of scope for advanced help.

And I am not sure if the deluge of READMEs and out of context popups that this would produce would be useful as API documentation, but that is for the API crowd to decide.