Please check if the PR fulfills these requirements
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:
What is the current behavior? (You can also link to an open issue here)
The name of the plugin is webpack-rails-manifest-plugin.
What is the new behavior?
After the rename the plugin name will be webpack-asset-pipeline.
Does this PR introduce a breaking change?
[x] Yes
[ ] No
If this PR contains a breaking change, please describe the following...
Impact: The plugin will be renamed and will not be available on the NPM
Migration path for existing applications: Replace the old library with the new one.
Github Issue(s) this is regarding: #27
Other information:
The tag line is not longer correct and needs to be updated. Opened for discussion here. The transition will be finished when #28 is completed. The release of v1.2.0 is on hold until this is completed, and since this should break the v2 version probably the milestone should be updated too.
In case we decide to use another name we can use this PR and it's diff as a base for the new name.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
The name of the plugin is
webpack-rails-manifest-plugin.What is the new behavior?
After the rename the plugin name will be
webpack-asset-pipeline.Does this PR introduce a breaking change?
If this PR contains a breaking change, please describe the following...
Other information:
The tag line is not longer correct and needs to be updated. Opened for discussion here. The transition will be finished when #28 is completed. The release of
v1.2.0is on hold until this is completed, and since this should break thev2version probably the milestone should be updated too.In case we decide to use another name we can use this PR and it's diff as a base for the new name.