-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
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
Type refinement doesn't work with optional chaining #6613
Comments
Hi @jbrown215, is this issue in team task list or it's not relevant yet? |
Not on our radar yet (afaik) |
Okay, thanks |
Bumping for visibility? |
V8 supports it now: https://v8.dev/features/optional-chaining |
Similar issue/inconsistency described here: #8106 (comment) |
Here's a simplified example (IMO). Is this something that the Flow team would like some help on? I would love for this feature to be added to flow! |
@mvitousek is currently working on this |
Was this ever implemented? |
It was implemented as of v0.114! If you check out the try-flow examples in this issue you'll see that they pass now. |
Confirmed, works in 0.114.0. Big improvement, thanks so much! |
https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVAXAngBwKZgCCYAvGAN5RxwD8AXGAM4YBOAlgHYDmAvulAFcOAYwxs4HMFA4AKAIYMahAJQNi5VGDBsoYeTQB0VOMoqatYFngwCWkuQG5zfLVZt2KxhgHIAJnig5ARgMbx4nPiA
The text was updated successfully, but these errors were encountered: