-
-
Notifications
You must be signed in to change notification settings - Fork 679
[vue/html-indent] wrong indentation reported with just one prop/attr #375
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
Comments
Thank you for the report. I confirmed it, and I will fix it. |
Hi, We still have the problem with the same config above :( |
Hey @iujlaki Are you sure you have the right version of eslint-plugin-vue installed? This reproduction seems to be working fine 🤔 |
Hey @michalsnik, yep it's the same. It's weird because it works on several Mac but in Linux it doesn't.
|
Perhaps you're running global eslint and have a plugin installed globally as well?
? |
We got the same error :( |
Show me your |
Hi, The versions are: "eslint-plugin-vue": "4.2.2", and our .eslintrc.js file contains:
Many thanks! 🙏 |
* Add Vue.extend support, add missing info about Vue.mixin check in readme * Docs: fixes wording in docs (#372) * Fix: fix script-indent to prevent removing <script> tag (fixes #367) (#374) * [Update] Make `vue/max-attributes-per-line` fixable (#380) * [Update] Make `vue/max-attributes-per-line` fixable * [fix] bug and style * [fix] Switch indent calculation method with node and attribute * [fix] don't handle indentation * [add] autofix test max-attributes-per-line.js * Update: make `vue/order-in-components` fixable (#381) * [Update] Make `vue/order-in-components` fixable This Commit makes `vue/order-in-components` fixable. In case of `The "A" property should be above the "B" property` error, autofix will move A before B * [fix] fail test at [email protected] * [fix] If there is a possibility of a side effect, don't autofix * [fix] failed test at node v4 * [update] use Traverser * [fix] failed test [email protected] * [fix] I used `output: null` to specify "not fix" * Fix: no-async-in-computed-properties crash (fixes #390) * Fix: valid-v-on false positive (fixes #351) * Fix: indent rules false positive (fixes #375) * [New] Add `prop-name-casing` * fix message and category * fix category * fix test message * Set category to undefined * Add more tests and fix edge case scenario * attribute order linting * updating docs, tests and category * [New] Add rule `vue/no-use-v-if-with-v-for` (#2) * [fix] `meta.docs.description` should not end with `.` consistent-docs-description * [fix] lint error caused by merging the master for conflict resolution * [fix] That `vue/attributes-order` got duplicated when merging README * [fixed] document `correct` and `incorrect` the contrary stated * [fixed] error message
Tell us about your environment
Please show your full configuration:
What did you do? Please include the actual source code causing the issue.
Reproduction online
What did you expect to happen?
I expect vue/html-indent error to not being reported in that case
What actually happened? Please include the actual, raw output from ESLint.
But if you add another prop after foo then it works as expected:
Am i missing something in my configuration? 🤔
The text was updated successfully, but these errors were encountered: