-
Notifications
You must be signed in to change notification settings - Fork 448
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
chore: update eslint-config-i18n to ^1.1.0 #6210
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
No changes to documentation |
Component Testing Report Updated Apr 4, 2024 4:32 PM (UTC)
|
bb365a0
to
480086e
Compare
@@ -9,6 +9,7 @@ import { | |||
} from '@sanity/ui' | |||
import type * as React from 'react' | |||
import {type ComponentProps, forwardRef} from 'react' | |||
//eslint-disable-next-line @sanity/i18n/no-i18next-import -- avoiding a circular import | |||
import {useTranslation} from 'react-i18next' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems problematic to import from sanity
here, and traversing up and down the file tree to get to core
also seems problematic at best.
Description
I received a request to review a renovabot PR that upped the version of this lint rule to not allow imports from
i18next
. Since we had those, it required a manual handling of those places where did previously import this.What to review
I've made the following changes:
structure
to import fromsanity
rather thani18next
.Testing
Does it pass our linting rules?