You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see that modifications to this can be a breaking change.
However, as it is currently implemented, it is not intuitive.
Besides a format that would be preferred (because it's shorter) and breaking, I see at least one way to add this functionality in a non-breaking way.
Example:
// extending from:
types: {
"svelte": true,
"wewanttogetridofthis": 1
}
// root
types: {
"node": true,
"jest": 1, // example to write it shorter
"wewanttogetridofthis": false // remove the dependency by making it falsy
}
It could be implemented in a way that the to-be-extended-from config can use arrays (equal to { dep1: true, dep2: true }) and the root, the referencing config uses the object notation.
Just as an inspiration.
Another, of course breaking, format change would be to introduce a "!" prefix to module names, allowing the referencing config to cancel a module name by adding !wewanttogetridofthis to the array. (Just for completeness.)
If you insist on not touching the compiler config system, could you/we at least add a note to the documentation at:
Formulating a proposed solution to microsoft/TypeScript#44597 ...
I see that modifications to this can be a breaking change.
However, as it is currently implemented, it is not intuitive.
Besides a format that would be preferred (because it's shorter) and breaking, I see at least one way to add this functionality in a non-breaking way.
Example:
It could be implemented in a way that the to-be-extended-from config can use arrays (equal to
{ dep1: true, dep2: true }
) and the root, the referencing config uses the object notation.Just as an inspiration.
Another, of course breaking, format change would be to introduce a "!" prefix to module names, allowing the referencing config to cancel a module name by adding
!wewanttogetridofthis
to the array. (Just for completeness.)If you insist on not touching the compiler config system, could you/we at least add a note to the documentation at:
?
The text was updated successfully, but these errors were encountered: