-
-
Notifications
You must be signed in to change notification settings - Fork 670
Fix asconfig merge order #1406
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
Fix asconfig merge order #1406
Conversation
Hmm, this is failing in apparently unrelated |
I had the same issue when I tried to delay the adding defaults to |
Really just trying to dig into merge order in separation here, as that's what I'm primarily concerned about. Wasn't expecting unrelated breakage, though, so if you'd like to incorporate the merge order (this PR has the correct one now) into your PR, feel free to do so. |
cli/asc.js
Outdated
seenAsconfig.add(filePath); | ||
asconfig = getAsconfig(fileName, asconfigDir, readFile); | ||
} | ||
asconfigPath = optionsUtil.resolvePath(asconfig.extends, asconfigDir); |
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.
Nice! I was going to mention that we should allow for node_resolution here like ts does.
#1408 Adds tests to this PR. |
Co-authored-by: Max Graey <[email protected]>
🎉 This PR is included in version 0.14.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Fixes the merge order part of #1404 by updating to the originally intended order
while moving the defaults for
target
andconfig
to asc itself because we need these early. Previously, the initial invocation ofparse
missed to omit populating defaults, and #1404 also seems to populate these too early.