-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Implicit arrow return of test function and timeout is hard to read #5365
Copy link
Copy link
Closed
Labels
lang:javascriptIssues affecting JSIssues affecting JSlocked-due-to-inactivityPlease open a new issue and fill out the template instead of commenting.Please open a new issue and fill out the template instead of commenting.status:has prIssues with an accompanying pull request. These issues will probably be fixed soon!Issues with an accompanying pull request. These issues will probably be fixed soon!
Milestone
Metadata
Metadata
Assignees
Labels
lang:javascriptIssues affecting JSIssues affecting JSlocked-due-to-inactivityPlease open a new issue and fill out the template instead of commenting.Please open a new issue and fill out the template instead of commenting.status:has prIssues with an accompanying pull request. These issues will probably be fixed soon!Issues with an accompanying pull request. These issues will probably be fixed soon!
Prettier 1.15.1
Playground link
Input:
Output:
Expected behavior:
Not sure, actually. But I find it pretty hard to read at first glance that
250is an argument toitand not part of the statement in the body of the callback function.Related to #5085 (FWIW, I'm highly supportive of that change, I just think the arrow return case is hard to read)