📝 Track optional discriminants under the union-property task
This commit is contained in:
1 parent
fcec637f01
commit
d88a4eeb45
1 file changed
+1
@@ -63,6 +63,7 @@ Matcher:
|
|||||||
☐ when using a union type as a property, the current behavior of tagged union matcher is
|
☐ when using a union type as a property, the current behavior of tagged union matcher is
|
||||||
to pass never to handler parameters
|
to pass never to handler parameters
|
||||||
→ new matcher function needed or can be fixed in tagged union matcher
|
→ new matcher function needed or can be fixed in tagged union matcher
|
||||||
|
☐ optional discriminant (`{ type?: "x" }`) is the same hole: the boolean/nullish change now admits the `undefined` tag, so the factory accepts the key, but `Extract<T, Record<K, V>>` still passes `never` to both the `x` and `undefined` handlers
|
||||||
|
|
||||||
Bugs:
|
Bugs:
|
||||||
✔ TS 7 LSP server logs `context canceled` on stderr at shutdown @done
|
✔ TS 7 LSP server logs `context canceled` on stderr at shutdown @done
|
||||||
|
|||||||
Reference in new issue
Block a user