chore: support custom configPath for createParsedCommandLineByJson #3456
+3
−2
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.
I want to parse config content after overriding and I found two methods:
createParsedCommandLine
andcreateParsedCommandLineByJson
.createParsedCommandLine
parse config via path and cannot specify the config content.createParsedCommandLineByJson
will always set config path torootDir + '/jsconfig.json'
.So it would be great if
createParsedCommandLineByJson
can support custom config path.