-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
import/no-empty-named-blocks
false positive in many cases
#2667
Comments
hmm, i can't seem to reproduce these. What eslint parser are you using? (i tried the default one) |
Either way, the entire implementation of this rule needs to be rewritten to solve #2666, so hopefully the next release will address this issue. |
v2.27.3 is released; give that a shot. |
It seems it's fixed in 2.27.4. |
JiriLojda
added a commit
to kontent-ai/eslint-config
that referenced
this issue
May 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Triggers from the last 3 files:
In every file all errors on 1:1 position. No one of them has empty named blocks.
The text was updated successfully, but these errors were encountered: