Restrict integration: 'legacy' to component tests. #122
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The meaning of `integration: true` has been the same for non-component tests, so only allow usage of `legacy` when using a component test.
* Update default dependencies (makes `ember test` run against current release). * Add 2.1.0 to ember-try config. * Add 2.2.0 to ember-try config. * Use associated Ember Data with each respective Ember release.
rwjblue
added a commit
that referenced
this pull request
Nov 23, 2015
Restrict integration: 'legacy' to component tests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The meaning of
integration: truehas been the same for non-componenttests, so only allow usage of
legacywhen using a component test.Update default dependencies & ember-try config.
ember testrun against currentrelease).