Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Should Features show empty packages with no configuration assigned to them?
Right now if you have a content type called "mycontent" that is defined in a module with a different name, such as "mymodule", Features will correctly assign the content type to "mymodule" but will also list a new blank features called "mycontent" in the not-exported section.
Wonder if we should be removing these blank packages at the end of processing assignment plugins, or if we create another assignment plugin to handle this task?
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | features_remove_empty_features-2697007-4.patch | 992 bytes | mpotter |
Comments
Comment #2
nedjoYeah, I can't see the point of showing packages that don't already exist and have no configuration assigned to them.
What if they do already exist (were previously exported and/or installed)? If they're now entirely empty, they may be deleted. But otherwise they may contain other code that's still needed. So it seems like we need to regenerate them, even empty.
Comment #3
mpotter commentedI think it might make sense to show empty packages if they are already exported (uninstalled or enabled). So this would just be to hide the empty not-exported packages.
Comment #4
mpotter commentedPatch for removing empty packages.
Comment #6
mpotter commentedCommitted to 93c5fcc.