IssueRaiser

Feature request: allow user to merge extended arrays in tsconfig files

**Scenario**: As a user, I would like to optionally merge extended arrays in `tsconfig` files. To do so, I would add a nested dot array `["..."]` reminding spread operator to the property I want to merge. Here is an example: <details> <summary><code>tsconfig-base.json</code></summary> <pre> { "exclude": ["**/__specs__/*"] } </pre> </details> <details> <summary><code>tsconfig-custom.json</code></summary> <pre> { "extends": "./tsconfig-base.json", "exclude": [["...tsconfig-base"], "lib"] // resolved to ["**/__specs__/*"; "lib"] } </pre> </details> <br/> **Alternative**: using a config `{}` object <details> <summary><code>tsconfig-custom.json</code></summary> <pre> { "extends": "./tsconfig-base.json", "exclude": [{ "extends": "tsconfig-base" }, "lib"] // resolved to ["**/__specs__/*"; "lib"] } </pre> </details>

Posted by jsamr on Nov 17, 2017, 8:22 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments

github (Other)

Feature request: allow user to merge extended arrays in tsconfig files

jsamrNov 17, 2017, 8:22 PM

**Scenario**: As a user, I would like to optionally merge extended arrays in `tsconfig` files. To do so, I would add a nested dot array `["..."]` reminding spread operator to the property I want to merge. Here is an example: <details> <summary><code>tsconfig-base.json</code></summary> <pre> { "exclude": ["**/__specs__/*"] } </pre> </details> <details> <summary><code>tsconfig-custom.json</code></summary> <pre> { "extends": "./tsconfig-base.json", "exclude": [["...tsconfig-base"], "lib"] // resolved to ["**/__specs__/*"; "lib"] } </pre> </details> <br/> **Alternative**: using a config `{}` object <details> <summary><code>tsconfig-custom.json</code></summary> <pre> { "extends": "./tsconfig-base.json", "exclude": [{ "extends": "tsconfig-base" }, "lib"] // resolved to ["**/__specs__/*"; "lib"] } </pre> </details>

Comments (0)

No comments yet. Start the discussion.

Comment on this issue