WriteV1Config: fix /tests support #1412
Merged
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.
Addresses #1387 (development config incorrectly loaded instead of test config when visiting
/tests
withtests: true
,storeConfigInMeta: false
)This PR applies the conditional logic suggested in #1387 (comment)
Example module output with `tests: true`
Example module output with `tests: false`
Answered questions about the implementation for this.
V1Config
with env hardcoded totest
and pass it in?tests: true
andfalse
shows the expected config being loadedsuper([inputTree, undefined])
equivalent tosuper([inputTree])
?scenario
. I'm tracking this work here (Add test scenario fortests: true
storeConfigInMeta: false
config 22a/embroider#1) instead of cluttering this PR with messy attempts to learn the scenario system