We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
vue/no-restricted-class
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
What rule do you want to change? vue/no-restricted-class
Does this change cause the rule to produce more or fewer warnings? No
How will the change be implemented? (New option, new default behavior, etc.)? Allow a regex pattern just like we did here
Please provide some example code that this change will affect:
<div class="ml-2" />
What does the rule currently do for this code? Right now to restrict the classes which are not RTL friendly I have to write long list of them:
'vue/no-restricted-class': ['error', 'ml-1', 'ml-2', /* And more... */],
What will the rule do after it's changed? Once this rule accept regex pattern we don't have to write long list, just below is enough:
'vue/no-restricted-class': ['error', '/^(m|p)(l|r)-/'],
Additional context None
The text was updated successfully, but these errors were encountered:
PRs welcome!
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
What rule do you want to change?
vue/no-restricted-class
Does this change cause the rule to produce more or fewer warnings?
No
How will the change be implemented? (New option, new default behavior, etc.)?
Allow a regex pattern just like we did here
Please provide some example code that this change will affect:
<div class="ml-2" />
What does the rule currently do for this code?
Right now to restrict the classes which are not RTL friendly I have to write long list of them:
What will the rule do after it's changed?
Once this rule accept regex pattern we don't have to write long list, just below is enough:
Additional context
None
The text was updated successfully, but these errors were encountered: