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

fix: eslint import/no-unresolved error #1791

Merged
merged 2 commits into from
Aug 14, 2024
Merged

fix: eslint import/no-unresolved error #1791

merged 2 commits into from
Aug 14, 2024

Conversation

ripecosta
Copy link
Contributor

Description

Address the ESLint error introduced in #1790. I was unable to understand why it was happening so I opted to add an ignore to it to unblock master.

Checklist

  • only relevant code is changed (make a diff before you submit the PR)
  • run tests npm run test
  • tests are included
  • commit message and code follows the Developer's Certification of Origin

@@ -13,6 +13,7 @@
"browser": true,
"node": true
},
"reportUnusedDisableDirectives": true,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will help spot if the import/no-unresolved gets fixed.

@coveralls
Copy link

coveralls commented Aug 14, 2024

Coverage Status

coverage: 97.073%. remained the same
when pulling 8a15dc4 on ripecosta:rc/import-error
into e068e5e on i18next:master.

@@ -369,7 +369,7 @@ export function Trans({
)
return;

// eslint-disable-next-line react/no-unstable-nested-components, no-inner-declarations
// eslint-disable-next-line react/no-unstable-nested-components
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Found after enabling reportUnusedDisableDirectives.
image

@adrai adrai merged commit f1fb5df into i18next:master Aug 14, 2024
9 checks passed
@ripecosta ripecosta deleted the rc/import-error branch August 14, 2024 14:39
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.

3 participants