-
-
Notifications
You must be signed in to change notification settings - Fork 696
Update order-in-components.md #2309
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
Conversation
That line is auto-generated from the rule:
And indeed, some problems can be auto-fixed, so the message in the documentation is not wrong.
@FloEdelmann Thank you for checking. Okay, It’s my misunderstanding.
By the way, there are definitely cases where this rule does not work, as actually reported in some of the issues, right?
Then I think it would be clearer to specify such cases in the documentation. What do you think?
Sure, explaining those cases in the documentation would be a good idea.
Uh oh!
There was an error while loading. Please reload this page.
Hi team, I have added modifications to the document.
Even though this rule does not support auto-fix, the documentation explained that it does. So I have removed it.
Honestly, I'm not sure why it cannot be fixed automatically, but it was mentioned in this comment (#1841 (comment)).
related: