-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Parsing Bug #18711
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
Labels
Duplicate
An existing issue was already created
Comments
I should note that prettier 1.5 did this, not 1.7 |
Slightly smaller repro here. Interestingly removing the second or third line break can fix it (
f([
() => { },
() => { }
])
) (Your playground link is a bit malformed btw, some extra #src stuff mixed in) |
Seems to be working for me. Can you try our nightlies (i.e. |
Sounds good to me! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
TypeScript Version: 2.5.2
Code
The following code doesn't parse correctly and Typescript thinks f is trying to be a function. This is particularly annoying when Prettier formats my code this way...
Example here
Expected behavior:
Actual behavior:
The text was updated successfully, but these errors were encountered: