We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
as
no-dynamic-keys
What rule do you want to change? @intlify/vue-i18n/no-dynamic-keys
@intlify/vue-i18n/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 (skipTSAsExpression)
skipTSAsExpression
Please provide some example code that this change will affect:
<template> <span>{{ t(`binary-question.${isPositive.toString()}.title` as `binary-question.${'true' | 'false'}.title` }}</span> </template> <script lang="ts" setup> let isPositive: bool = true; </script>
What does the rule currently do for this code? Disallow any dynamic translation key
What will the rule do after it's changed? Only disallow dynamic translation keys when their type isn't narrowed down via template string literal type.
Additional context
The text was updated successfully, but these errors were encountered:
no-unused-keys
No branches or pull requests
What rule do you want to change?
@intlify/vue-i18n/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 (
skipTSAsExpression
)Please provide some example code that this change will affect:
What does the rule currently do for this code?
Disallow any dynamic translation key
What will the rule do after it's changed?
Only disallow dynamic translation keys when their type isn't narrowed down via template string literal type.
Additional context
The text was updated successfully, but these errors were encountered: