Features has always been a combination of two modules: creating features and providing export for items that don't have exports. This has led to a lot of confusion on what features is, and has made handling those particular exports complicated as they don't have their own ui/way to export/etc.

Features export

  • Included with features, but not dependent
  • Includes minimal UI/drush commands to import/export/revert/etc. single components?
  • Include exporting of component types features currently supports

Could also be moved to a separate project outside of features.

Which leaves features to:

  • Includes ui/drush to create a feature.
  • Includes current integration to make existing exportables (ctools) features comparable
  • Includes functional to revert/rebuild entire features.

This would likely be a new architecture (features-2.x)

Comments

Grayside’s picture

Grayside commented

Another major goal for separation of export from UI/workflow management is clear the decks for migration of Features into D8/Configuration Management. Ideally, a large amount of that upgrade would involve deleting most of this Features Export module and extending the ideas in the CTools integration with Features to CMI generally.

Cons with separate project: Anyone going to use Features already struggles to remember to turn on Strongarm. Now they have to turn on Features Export as well. I almost wonder if there should be drush features-get-started to turn on all the modules that match the 90% use case..

mpotter’s picture

mpotter commented
Status: Active » Postponed

Postponed till v2.x work (likely in conjunction with D8 CMI since that will drastically change Features)

hefox’s picture

hefox commented
Issue summary: View changes
Status: Postponed » Closed (won't fix)