Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Enhancement: [consistent-type-assertion] Bring in options from total-functions/no-unsafe-type-assertion#6011
-
Before You File a Proposal Please Confirm You Have Done The Following...
My proposal is suitable for this project
Link to the rule's documentationhttps://typescript-eslint.io/rules/consistent-type-assertions Descriptionhttps://github.com/danielnixon/eslint-plugin-total-functions#total-functionsno-unsafe-type-assertion has some useful options:
Can we add these options to FailtypeFoo={readonlybar:number};constfoo={};constfoo2=fooasFoo;foo2.bar.toString(); PasstypeFoo={readonlybar:number};constfoo={};constfoo2=fooasPartial<Foo>;foo2.bar?.toString(); Additional InfoForking conversation out fromdanielnixon/eslint-plugin-total-functions#665. |
BetaWas this translation helpful?Give feedback.
All reactions
Replies: 1 comment
-
TBH I really hate One big problem is that you can do I think we need to take a look at this rule and really evaluate the point of it and what we might do better. |
BetaWas this translation helpful?Give feedback.
All reactions
This discussion was converted from issue #5953 on November 17, 2022 15:53.