You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The plugin insists on removing the delimiting empty line between the imports and a semicolon. This affects, for example, inline function calls (which are prepended with a semicolon by prettier).
Good catch, I didn’t think about semicolon-less JS style. The plugin thinks that the semicolon belongs to the import statement (although with weird whitespace).
The plugin insists on removing the delimiting empty line between the imports and a semicolon. This affects, for example, inline function calls (which are prepended with a semicolon by prettier).
Example:
See screenshots:
The "fixed" version:
Expected behaviour
Allow empty line between imports and a block starting with a semicolon (as on screenshot 1).
If you need a reproduction repo I can create one. But I think the problem will repeat if you just copy/paste my example to any environment.
The text was updated successfully, but these errors were encountered: