Lookup tsconfig.json from location of dangerfile #1068
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
orta
approved these changes
Sep 3, 2020
| expect(dirContains(`c:\\a`, `c:\\a`)).toBe(true) | ||
| expect(dirContains(`c:\\a`, `d:\\a\\b`)).toBe(false) | ||
| expect(dirContains(`c:\\a`, `d:\\a`)).toBe(false) | ||
| }) |
|
if we get another PR landing soon I'll ship this with that, otherwise I'll do it in a few days |
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.
Closes #1067
Now ts transpiler looks for
tsconfig.jsonfile starting from the location of the danger file. If the current directory is an ancestor of that location, it climbs up to it and returns the first found config file. Otherwise only additionally checks the current working directory.cc @orta