-
-
Notifications
You must be signed in to change notification settings - Fork 666
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
Make attributes "buckets" configurable #2514
Comments
Instead of |
I would like a possibility to just add some attributes without the need to redefine all existing ones nor the order of the buckets. But I will try the suggested solution. Just to be sure, because that's not in the docs: I have to configure the |
That did not work: 'vue/attributes-order': [
'error',
{
order: [
'DEFINITION',
'LIST_RENDERING',
'CONDITIONALS',
'RENDER_MODIFIERS',
'GLOBAL',
/* UNIQUE: */ ['ref', 'key', /* added: */ 'row-key'],
'TWO_WAY_BINDING',
'OTHER_DIRECTIVES',
'OTHER_ATTR',
'EVENTS',
'CONTENT'
],
alphabetical: false
}
]
|
What rule do you want to change?
vue/attributes-order
Does this change cause the rule to produce more or fewer warnings?
The same as before.
How will the change be implemented? (New option, new default behavior, etc.)?
More flexible configuration, e.g. by adding options.
Please provide some example code that this change will affect:
Quasar uses
row-key
inq-table
that is IMO similar tokey
used forv-for
.Currently, I cannot order these to the same position, see examples below.
What does the rule currently do for this code?
What will the rule do after it's changed?
By adding
row-key
toUNIQUE
, it would allow:The text was updated successfully, but these errors were encountered: