Skip to content

Commit a235c5f

Browse files
committed
fix: disable exactOptionalPropertyTypes for now
Even popular libraries can't easily migrate to this option at the moment. I think we need 1. more consensus on whether this should be the default in the Vue.js ecosystem, and 2. a softer way to push this forward before making it a type error.
1 parent c2c92d6 commit a235c5f

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

tsconfig.json

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,9 @@
3434
// See <https://www.semver-ts.org/formal-spec/5-compiler-considerations.html#strictness>
3535
// These 2 options are also part of the recommended tsconfig as of TS 5.9
3636
"noUncheckedIndexedAccess": true,
37-
"exactOptionalPropertyTypes": true,
37+
// Commented out for now. It's hard to land in the current ecosystem.
38+
// Needs more consensus before moving forward.
39+
// "exactOptionalPropertyTypes": true,
3840

3941
// <https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#verbatimmodulesyntax>
4042
// Any imports or exports without a type modifier are left around. This is important for `<script setup>`.

0 commit comments

Comments
 (0)