Description
Summary
According to #2258 (comment)
Added "project" option in typescript.json with identical semantics to the tsc --project parameter
However, when a heft project is rigged, in rig's configuration, it is unclear which tscconfig.json the configuration is read from, and the result is in effect that the typescript task being disabled as described in #2258 (comment):
Using the "project" option in typescript.json introduced in #2844, you can set it to a non-existent file and that will disable the plugin execution.
Repro steps
Set up a rigged heft project and specify a custom tsconfig.json in the project
field. See example repo:
Expected result:
Expect the specified tsconfig.json to be adopted and the typescript task run.
Actual result:
Typescript task is disabled
Details
Detailed discussion in zulip:
Standard questions
Please answer these questions to help us investigate your issue more quickly:
Question | Answer |
---|---|
@rushstack/heft version? |
0.37.0 |
Operating system? | Mac |
Would you consider contributing a PR? | Not right now |
Node.js version (node -v )? |
v14.17.3 |
Metadata
Metadata
Assignees
Labels
Type
Projects
Status