Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Problem/Motivation
Because they're used for namespacing, most or all features developers will want to first create a bundle before generating features. However, currently, the first screen to appear on initial install is the feature generation one, with "Default" selected for "Bundle". Users may proceed to generate features and only later discover that they should first have created one or more bundles.
Even if they first look around and bring up the admin/config/development/features/bundle screen, there's not a lot to go on in order to understand what a bundle is and why you would create one.
Proposed resolution
If no bundles have yet been created, at admin/config/development/features generate a message. Draft:
You have not yet created any bundles. Before generating features, you may wish to [link]create a bundle[/link] to group your features within.
(Moved to #2653166: Provide message if no custom bundle created.)
Amend help text at admin/config/development/features/bundle. Draft:
Bundles are used to collect together groups of features. A bundle provides a shared namespace for all features included in it, which prevents conflicts and helps distinguish your features from those produced for other purposes. Common uses of bundles include:
- Custom features for use on a particular site.
- The features of a given distribution.
Use the form below to manage bundles. Each bundle comes with a set of assignment methods. By configuring and ordering the assignment methods, you can set the defaults for what does and doesn't get packaged into features for your bundle. Use the Bundle select to choose which bundle to edit, or chose --New-- to create a new bundle. The Default bundle does not include a namespace and cannot be deleted.
Remaining tasks
User interface changes
API changes
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 2490818-7.patch | 1.72 KB | nedjo |
| |||
Comments
Comment #1
mpotter CreditAttribution: mpotter commentedI'm not sure I want to force people to use bundles. It's really easy to move a feature into a bundle at a later time (edit the feature, select the bundle, export). So I'm not sure we need to change the first screen. I'm not a fan of putting a ton of help text onto the screen. That's the kind of stuff that really belongs in the Readme file.
So maybe this issue could create a patch for adding help to the Readme?
Comment #2
colanI like the original plan. I don't see the problem with having the information upfront. (Aside: The text looks good to me.)
I don't know if I speak for everyone else, but I only look at READMEs if the usage isn't self-explanatory. Actually, I'd rather do away with READMEs in general in favour of UIs that provide all of the necessary information.
Comment #3
nedjoAttached patch generates a message if there are no custom bundles and adds the help text.
Comment #4
nedjoRemoving company attribution.
Comment #5
nedjoRemoving company attribution.
Comment #6
nedjoOn second thought, the message should go in a distinct issue, because it should have a test and shouldn't hold up the help text improvement.
Comment #7
nedjoMoved part of this to #2653166: Provide message if no custom bundle created. Patch is now limited to adding help text.
Comment #9
nedjoComment #10
nedjo