Skip to content
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(i18n): add the i18next/no-literal-string eslint rule #4998

Closed
wants to merge 163 commits into from

Conversation

jtpetty
Copy link
Contributor

@jtpetty jtpetty commented Oct 16, 2023

Description

This PR adds an eslint rule that will fail if the javascript file contains literal English strings.

snorrees and others added 30 commits October 9, 2023 13:52
We generally prefer interfaces, but this in particular allows us to extend the
type from the `sanity` module using declaration merging. While not the optimal
choice (the whole type should really just be in the `sanity` module), it is at
least addressing the problem until we can do a breaking change in the types
module.
Because there can be several validation errors/warnings/info messages for a
single field, simply using the field path as key is not enough, since React only
renders a single element per parent with a given key.
This is required because non-React codepaths will simply fail/throw when
attempting to use a namespace that is not defined. An example is the upcoming
validation system, where the validation system is decoupled from the React
lifecycle, and so cannot rely on Suspense in order to load missing namespaces.
rexxars and others added 22 commits October 11, 2023 13:03
Makes it easier to see which areas are not yet localized
@vercel
Copy link

vercel bot commented Oct 16, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
performance-studio 🔄 Building (Inspect) Visit Preview Oct 16, 2023 8:08pm
test-studio 🔄 Building (Inspect) Visit Preview Oct 16, 2023 8:08pm
1 Ignored Deployment
Name Status Preview Updated (UTC)
studio-workshop ⬜️ Ignored (Inspect) Oct 16, 2023 8:08pm

@github-actions
Copy link
Contributor

Component Testing Report Updated Oct 16, 2023 8:18 PM (UTC)

File Status Duration Passed Skipped Failed
formBuilder/ArrayInput.spec.tsx ✅ Passed (Inspect) 6s 3 0 0
formBuilder/inputs/PortableText/Annotations.spec.tsx ✅ Passed (Inspect) 10s 3 0 0
formBuilder/inputs/PortableText/Decorators.spec.tsx ✅ Passed (Inspect) 10s 6 0 0
formBuilder/inputs/PortableText/Input.spec.tsx ✅ Passed (Inspect) 12s 9 0 0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx ✅ Passed (Inspect) 45s 18 0 0
formBuilder/inputs/PortableText/Styles.spec.tsx ✅ Passed (Inspect) 10s 6 0 0
formBuilder/inputs/PortableText/Toolbar.spec.tsx ✅ Passed (Inspect) 5s 3 0 0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants