NodeStream Core contains a handy drush command (ns-core-devel-enable/ns-core-devel-disable) that enables/disables development modules, like Views UI, Rules UI, Devel etc.
Would it be reasonable to extend the list of these modules with Deployment UI?

CommentFileSizeAuthor
#1 ns_core-add-deploy_ui-to-devel-modules-1578124-1.patch311 bytesbalintbrews

Comments

balintbrews’s picture

balintbrews
he/him/his
Primary language Hungarian
Location Netherlands 🇪🇺
commented
Status: Active » Needs review
StatusFileSize
new ns_core-add-deploy_ui-to-devel-modules-1578124-1.patch311 bytes

If so, here is the patch.

fabsor’s picture

fabsor commented
Title: Add Deployment UI to the list of development modules » Make the ns-core-devel-enable command extendable
Priority: Minor » Normal
Status: Needs review » Needs work

This would require that we actually include deploy in NodeStream which is another matter entirely. I probably wouldn't be against it though, as long as we find a proper use case for it in core.

I think a better idea would be to add a hook, "hook_ns_core_devel_modules", so that other modules (or installation profiles) can add whatever modules they consider development modules here. This would make the command more powerful and it would work across any site that uses NodeStream.