- last update
over 1 year ago run-tests.sh fatal error - Status changed to Needs review
over 1 year ago 10:58am 3 July 2023 - last update
over 1 year ago 69 pass
During the development of a site, developers should almost always use the same custom bundle to export features related to that site. This means that every time they export a feature (at least between sessions) they have to make sure to manually select the correct bundle.
One option would be if the "default" bundle could be saved as a config value. Note that this is not the "default" bundle that's provided out of the box by Features, but rather the ability to set any bundle as the default bundle.
However, there are issues with that approach. We currently store the default bundle in a session variable. If we add a new default
setting to features.settings
, we have to map out the interaction between the session variable and the new setting. Also, we have to set the initial value to default
(since, in Features itself, we can't count on any other value being present).
Alternatives:
Instead:
Needs review
5.0
User interface
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.