We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#13783
any
// @ts-ignore
never
in
#38162
type MaybeFoo = { bar: string; foo?: number; }; type AlwaysFoo = { foo: number | undefined; always: string; }; declare const f: AlwaysFoo & MaybeFoo; if ("foo" in f) { f.bar; } else { // 3.8.3: f: AlwaysFoo & MaybeFoo // 3.9: 'f' is 'never' f.bar; }
But that's the right behavior - similar to
type AlwaysFoo = { foo: number | undefined; bar: string; always: string; }; declare const f: AlwaysFoo;
Users were feature testing for a value on globalThis, but now have no clean way to do it.
globalThis
Conclusion: If we can special-case for globalThis, let's do it. If we can't get it in by end-of-day, back it out prior to 3.9, add it to 4.0.
deleteCount
splice
#32638
.apply
.bind
export =
#37964
Module augmentations occur before the calculation of the global Object type, global namespaces, etc.
Object
Currently, code that does this crashes, but what should we do when you write this?
import {toString} from "./foo";
What's this break?
Also have to figure out other features that are impacted here.
Conclusion: need to issue an error - the circularity has to end somewhere.
#34547 (comment)
#37920
noImplicitAny
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Unexpected Breaking Changes
Deletes on Non-Optional Properties
#13783
any
cast or// @ts-ignore
Intersections narrowed to
never
within
#38162
But that's the right behavior - similar to
Users were feature testing for a value on
globalThis
, but now have no clean way to do it.Conclusion: If we can special-case for
globalThis
, let's do it. If we can't get it in by end-of-day, back it out prior to 3.9, add it to 4.0.deleteCount
Optionality insplice
#32638
.apply
and.bind
export =
and Declarations Types#37964
Module augmentations occur before the calculation of the global
Object
type, global namespaces, etc.Currently, code that does this crashes, but what should we do when you write this?
export =
module.What's this break?
Also have to figure out other features that are impacted here.
Conclusion: need to issue an error - the circularity has to end somewhere.
JSX Factory Updates
#34547 (comment)
Control Flow for Constructor-Initialized Properties
#37920
noImplicitAny
?The text was updated successfully, but these errors were encountered: