Challenges with `exactOptionalPropertyTypes: true` in TypeScript Configuration
Did anyone else have issues adding the recommended
I have got about 70+ errors and some of them are from my shadcn components which isn't a bad thing, it just means if I ever override them, I'll need to update them to follow this rule.
On another note, did anyone find a way to autofix/patch there project to adhere to the
exactOptionalPropertyTypes: trueI have got about 70+ errors and some of them are from my shadcn components which isn't a bad thing, it just means if I ever override them, I'll need to update them to follow this rule.
On another note, did anyone find a way to autofix/patch there project to adhere to the
exactOptionalPropertyTypesThis rule enforces you do not use the optional param/property ? i.e.must become{ someValue?: string }so you explicitly have to pass{ someValue: string | undefined }toundefinedsomeValue
ON a sidenote: I do like the explicitness of this rule.
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
