-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
Key paths containing javascript built-ins are handled inconsistently #1838
Labels
🔨 p3-minor-bug
Priority 3: a bug in an edge case that only affects very specific usage
Status: PR Welcome
Welcome to Pull Request
Type: Bug
Bug or Bug fixes
Comments
kazupon
added
Type: Bug
Bug or Bug fixes
🔨 p3-minor-bug
Priority 3: a bug in an edge case that only affects very specific usage
and removed
Status: Review Needed
Request for review comments
labels
May 6, 2024
related #1711 |
Happy to provide a fix if the correct behaviour is known 🙂 |
Current failures:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
🔨 p3-minor-bug
Priority 3: a bug in an edge case that only affects very specific usage
Status: PR Welcome
Welcome to Pull Request
Type: Bug
Bug or Bug fixes
Reporting a bug?
Similar to
vue-i18n
, using javascript builtins in key paths can have surprising results.Ref:
Expected behavior
Keys should be handled consistently, or explicitly rejected if not supported.
Reproduction
https://github.com/intlify/vue-i18n-next/compare/master...alxndrsn:builtins?expand=1#diff-38b7f4833b6d1b2e7a9f81900841139df0e91381af1eae14cdb1f1ce432f465a
Example results:
System Info
Screenshot
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: