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

Disable ESlint false positive #1198

Merged
merged 1 commit into from
Feb 14, 2025
Merged

Conversation

MikeTaylor
Copy link
Contributor

It's complaining about import/no-named-as-default when the import is perfectly cromulent. Community consensus seems to be just to disable it when this happens.

This gives us a clean lint, which is the baseline I want to work from.

It's complaining about import/no-named-as-default when the import is
perfectly cromulent. Community consensus seems to be just to disable
it when this happens.

This gives us a clean lint, which is the baseline I want to work from.
Copy link

Jest Unit Test Results

    1 files  ±0    186 suites  ±0   1m 12s ⏱️ -2s
1 982 tests ±0  1 982 ✅ ±0  0 💤 ±0  0 ❌ ±0 
2 022 runs  ±0  2 022 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 37f9b6a. ± Comparison against base commit 6ab6cd6.

@MikeTaylor MikeTaylor merged commit 09c8979 into master Feb 14, 2025
15 checks passed
@MikeTaylor MikeTaylor deleted the disable-eslint-false-positive branch February 14, 2025 13:21
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.

1 participant