-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove blueprints that will be provided by: #4909
Conversation
code climate is going to love you for this! |
654e99c
to
792e34d
Compare
☔ The latest upstream changes (presumably #4915) made this pull request unmergeable. Please resolve the merge conflicts. |
792e34d
to
6cdb5f6
Compare
☔ The latest upstream changes (presumably #4920) made this pull request unmergeable. Please resolve the merge conflicts. |
* ember: emberjs/ember.js#12412 * ember-legacy-blueprint-addon: https://github.com/ember-cli/ember-cli-legacy-blueprints
6cdb5f6
to
5435d26
Compare
☔ The latest upstream changes (presumably #4692) made this pull request unmergeable. Please resolve the merge conflicts. |
fix model relationship name generation It is not currently possible to generate a model with a relationship named differently from the model's name ([despite the help indicating it should be](https://github.com/ember-cli/ember-cli/blob/master/blueprints/model/HELP.md)) This patch brings the code's behavior in line with the docs. The blueprint part of this patch will be obsoleted if #4909 lands, so I've also PRed the changes to the blueprint in ED: emberjs/data#3885 (the arg-parsing-fix part of this patch is still needed to pass a distinct name, though)
obsoleted by #5648 |
Add ember-cli-legacy-blueprints as internal dependency and remove blueprints and tests This PR resolves #5631 and #4909 - [x] Add ember-cli-legacy-blueprints as internal dependency - [x] Remove blueprints provided by ember-cli-legacy-blueprints - [x] Remove unnecessary tests covered by ember-cli-legacy-blueprints - [x] Fix any tests affected by blueprint removal (help .json output, etc)
clearly without the blueprints we will have many test failures, once we depend on addonified ember, those may stop. We should still extract nice blueprint test helpers for the various extracted addons to use.