-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Bug] Required semicolons incorrectly removed (semi: false config) #218
Comments
Thanks for the report! |
this will probably solved when glint moves to content-tag instead of ember-template-imports. |
Unfortunately I still seem to be having this issue (I'm on glint 1.4.0) This repo has the issue replicated (see the failing test I wrote) but does not depend on glint, so I am not sure if glint version matters, but I am no expert here
I want to mention a caveat to the workaround I gave in the description, is that if applied to anything more complex it disables prettier for that entire block class Abc extends Component {
fetchStats = trackedFunction(this, async () => {
// all of this inside the function is ignored by prettier
}); /* prettier-ignore */ /* prettier-ignore-end */
<template> ... |
@Techn1x is the issue about glint or prettier removing semicolon? |
🐞 Describe the Bug
I have
semi: false
in my prettier config. In general this works, but a semicolon is required between certain statements in a class and the<template>
tag. This plugin seems to remove those required semicolons when it shouldn't. This then causes glint errors.Example where the semicolon is required - prettier removes it, when it shouldn't.
🔬 Minimal Reproduction
Added failing test snapshot
#219
😕 Actual Behavior
prettier --write .
(resulting in glint errors)
🤔 Expected Behavior
prettier --write .
🌍 Environment
➕ Additional Context
I was having this issue before v2.0.0 as well, so it's not a regression.
A workaround is to disable prettier for the line that the semicolon is on, exactly like this
That looks really weird, but it "works" - I believe the weirdness is because I don't think this addon parses prettier-ignore directives correctly?
The prettier-ignore-end is important so that prettier is reenabled for the lines afterward
The text was updated successfully, but these errors were encountered: