What do you think about a rule, which checks whether a variable can be made read-only?
Read-Only is a TypeScript 2 Feature. The rule could maybe determined by checking whether a field is assigned only inside the constructor or the field will be initialized at the same place like the declaration.
TimBo93
All 7 comments
yeah, this could be pretty cool; it's similar in spirit to the prefer-const rule (https://github.com/palantir/tslint/issues/491)
adidahiya
on 13 Oct 2016
Perhaps an extension of this would be a functional-programming-only rule that ensures all function inputs are marked with the Readonly<T> annotation
dyst5422
on 28 Jul 2017
Just found https://www.npmjs.com/package/tslint-immutable - Super!
dyst5422
on 28 Jul 2017
Scratch that, definitely does not check function inputs. Will put an issue on that project though as it seems more tuned to this type of rule.
dyst5422
on 28 Jul 2017
It should be configurable for access modifiers. public and protected properties could be assigned outside of the current class context.
akosyakov
on 1 Aug 2017
KurtPreston
on 12 Jan 2018
Fixed by #2896
adidahiya
on 12 Jan 2018
Related issues
ghost
路
3Comments
adidahiya
路
3Comments
denkomanceski
路
3Comments
mateiacd
路
3Comments
sumitkmr
路
3Comments
Most helpful comment
yeah, this could be pretty cool; it's similar in spirit to the
prefer-construle (https://github.com/palantir/tslint/issues/491)