-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Don't use ember-cli project
instance outside of ember-cli commands
#1036
Don't use ember-cli project
instance outside of ember-cli commands
#1036
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1036 +/- ##
==========================================
+ Coverage 95.49% 95.54% +0.04%
==========================================
Files 21 21
Lines 511 516 +5
==========================================
+ Hits 488 493 +5
Misses 23 23 ☔ View full report in Codecov by Sentry. |
Still need to update getting the config without a |
f747ca7
to
951a41e
Compare
if (versionCompatibility) { | ||
// Required lazily to improve startup speed. | ||
let autoScenarioConfigForEmber = require('ember-try-config'); | ||
|
||
let autoConfig = await autoScenarioConfigForEmber({ | ||
versionCompatibility, | ||
project: options.project, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does not seem to be used by ember-try-config
?
Part of decoupling
ember-try
fromember-cli
.This way, only the code in
lib/commands
is coupled toember-cli
.The next step would be to move the
run
portion of the commands to separate files.This would allow us to move everything to ES modules, except the commands.
The commands can async import and run the ES modules.