The "Version:" should be HEAD but that isn't selectable.

I'm thinking that this is a useful module and am planning to use it for a site I'm developing but I find the API not fluid and not protected with the module namespace. I am going to use hook_action_info as an example in the explanation but my request is for all of the API not just this one, and I will use a module name of foo for the example of a module. The _info part of the API is the part of hook_action_info that I don't find fluid. It doesn't feel natural to use foo_action_info when I want to create the hook for the action; I want to instead write foo_workflow_ng_action which gives a namespace to the module being used and ends the name of the function with the type of data (info) being requested.

Would you be open to patches that change the names of the API to be namespaced as I've exampled above?

Comments

fago’s picture

Status: Active » Postponed

no - it's not possible any more as it would break compatibility of existing implementations.

anyway, things have been improved for 6.x - there the hooks are namespaced too.