-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
--fix mode not fixing anything with eslint-plugin-script-tags. #9142
Comments
After running eslint, I get this in my repo:
but just not |
I'm using |
Thanks for the report. This is working as intended because It's possible that this will be supported soon (see #9090), although it's likely that some changes will be required in |
@not-an-aardvark Ah, thanks! So, for people that make processors, what's the way in which they should handle it (so --fix mode works) so I can relay the message back to them? |
Here's the related issue on eslint-plugin-script-tags. |
My recommendation to processor developers would be to wait until #9090 is hopefully merged sometime in the near future, and then update their processors to also transform autofix ranges (as described in #9090) to make autofixing work properly. That said, it would also be useful for the ESLint team to get some implementation feedback earlier -- if anyone wants to update a processor to implement the experimental API in #9090 before it's merged, we'd like to hear about any implementation difficulties/inconveniences you encounter, so that we can modify the API appropriately. However, it's not guaranteed that the current form of the API is the final version that will be shipped (or that this enhancement will be shipped at all), so I would only do this if you're okay with the possibility of needing to change the implementation later on. |
Closing because this is working as intended. |
Tell us about your environment
What parser (default, Babel-ESLint, etc.) are you using? default
Please show your full configuration:
Configuration
What did you do? Please include the actual source code causing the issue.
I made a reproduction here: https://github.com/trusktr/gulp-eslint/tree/issue-204
Also see adametry/gulp-eslint#204 for more description of the issue.
What did you expect to happen?
Basically I expect
--fix
mode to also modify the content of my<script>
tags because I'm usingeslint-plugin-script-tags
to lint those parts of.hbs
or.html
files, etc.What actually happened? Please include the actual, raw output from ESLint.
No fixing happens in
.hbs
file, for example, only in.js
files.The text was updated successfully, but these errors were encountered: