Uh oh!
There was an error while loading. Please reload this page.
chore(typescript): uniformly access all index signature with index ac… - #15206
Conversation
…cess. This is a strictness check that we are going to enforce in g3 internal typescript, to aid with optimization. Generally it is also syntactically a good idea to have visual indication when a type is accessed through an index signature vs not.
rkirov
commented
Feb 19, 2019
Jeremy tells me I shouldn't have clicked on the big green button. Apologies to the caretaker, feel free to rollback as needed. |
I'm thinking if it would be possible to create a lint rule for this that enforces this type of property access. At first glance it looks like we could easily end up introducing new incorrect property accesses. |
…cess. (#15206) This is a strictness check that we are going to enforce in g3 internal typescript, to aid with optimization. Generally it is also syntactically a good idea to have visual indication when a type is accessed through an index signature vs not.
This is a follow up to angular#15206, with these two changes all of material in conforming. A build-time check to enforce this is part of tsetse - https://tsetse.info/property-renaming-safe but I don't know how to turn it on for this repositories bazel builds.
rkirov
commented
Mar 19, 2019
Better than a lint rule, we have a bazel tsetse check - https://tsetse.info/property-renaming-safe, however I don't know how to turn it on for your repo. |
…#15523) This is a follow up to #15206, with these two changes all of material in conforming. A build-time check to enforce this is part of tsetse - https://tsetse.info/property-renaming-safe but I don't know how to turn it on for this repositories bazel builds.
Adds a lint rule to help catch cases like angular#15206 until we can get something going through tsetse. Note this is only scoped to `ngOnChanges` and accesses of the `SimpleChanges` objects since that's where we've been having issues.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
…cess.
This is a strictness check that we are going to enforce in g3 internal
typescript to aid with optimization. Generally, it is also syntactically
a good idea to have visual indication when a type is accessed through an
index signature vs not.