The team has concluded that the current approach of having a single revision-data plugin with data generators is inferior to having a family of revision-data plugins that you can choose from.
The reasons for this are 1) consistency (why have to learn a data generator API when you already know how to use/create plugins, 2) flexibility (data generators all have to run during the same hook in the current plugin, while dedicated plugins could execute the hook(s) that is most suitable).
Action items:
The team has concluded that the current approach of having a single revision-data plugin with data generators is inferior to having a family of revision-data plugins that you can choose from.
The reasons for this are 1) consistency (why have to learn a data generator API when you already know how to use/create plugins, 2) flexibility (data generators all have to run during the same hook in the current plugin, while dedicated plugins could execute the hook(s) that is most suitable).
Action items:
ember-cli-deploy-git-revision-dataplugin (https://github.com/achambers/ember-cli-deploy-git-revision-data) (@achambers)ember-cli-deploy-git-revision-data plugintoember-cli-deployorg and grant npm privileges (@achambers)ember-cli-deploy-md5-revision-data pluginto repo inember-cli-deployorgember-cli-deploy-git-revision-dataplugin