You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this change cause the rule to produce more or fewer warnings?
Fewer
How will the change be implemented? (New option, new default behavior, etc.)?
New option. I'm imaging something similar as the ignores option for no-unused-keys.
Users would be able to put all their dynamic keys in one place and not get errors.
Please provide some example code that this change will affect:
What does the rule currently do for this code?
Give an error/warning
What will the rule do after it's changed?
Allow the user to set a pattern to ignore dynamic keys with a certain pattern.
Additional context
The way we would use it in our project would be to use the same pattern for no-unused-keys and no-dynamic-keys. We currently get some keys from the API that we use to lookup in the locale files. Changing the API would be difficult and making the keys not dynamic would result in a lot of unneeded boilerplate.
I am willing to work on this, if a PR is welcome.
The text was updated successfully, but these errors were encountered:
What rule do you want to change?
no-dynamic-keys
Does this change cause the rule to produce more or fewer warnings?
Fewer
How will the change be implemented? (New option, new default behavior, etc.)?
New option. I'm imaging something similar as the
ignores
option forno-unused-keys
.Users would be able to put all their dynamic keys in one place and not get errors.
Please provide some example code that this change will affect:
What does the rule currently do for this code?
Give an error/warning
What will the rule do after it's changed?
Allow the user to set a pattern to ignore dynamic keys with a certain pattern.
Additional context
The way we would use it in our project would be to use the same pattern for
no-unused-keys
andno-dynamic-keys
. We currently get some keys from the API that we use to lookup in the locale files. Changing the API would be difficult and making the keys not dynamic would result in a lot of unneeded boilerplate.I am willing to work on this, if a PR is welcome.
The text was updated successfully, but these errors were encountered: