Refactor ember-try scenarios. #831
Merged
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
* Use async/await for config/ember-try.js * Add ember-classic try scenario * Remove ember-without-application-wrapper scenario (tested in ember-classic scenario now) * Fix bug in ember-lts-3.16 scenario (it was testing 3.4 😭 )
rwjblue
force-pushed
the
refactor-try-scenarios
branch
from
f0225d5
to
0df3ed9
Compare
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.
ember-classic scenario now)
ember-lts-3.12andember-lts-3.16scenario (they wer testing 3.4 😭 )octaneby defaultCloses #316