Skip to content

Fix standard lint errors on main - #259

Merged
MonilBhavsar merged 1 commit into
mainfrom
nicolas-fix-lint
Sep 7, 2026
Merged

MonilBhavsar merged 1 commit into
mainfrom
nicolas-fix-lint

Conversation

@NicolasBonet

@NicolasBonet NicolasBonet commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Details

Fixes all npm run lint (standard 'src/**/*.js') errors on main by running standard --fix. The changes are formatting only: double quotes converted to single quotes, semicolons removed, trailing commas removed, indentation normalized to 2 spaces, and standard function/JSX spacing applied. No logic changes — the diff is entirely mechanical output of the auto-fixer, verified by re-running the linter (clean exit).

What this fixes

npm run lint fails on a clean checkout of main with dozens of style errors in src/index.js, src/utils.js, src/LogoSVG/, and src/__tests__/QRCode-test.js, which makes lint useless as a CI signal for real changes. No related issue.

Note: npm test also fails on main, but for an unrelated pre-existing reason (Babel config error Unknown option: .disableImportExportTransform — all suites fail before running any test), so it is equally broken before and after this PR.

Checklist

  • I have described the bug/issue
  • I have provided reproduction in Example App
  • I have tested that solution works on Example App on all platforms:
    • Android
    • iOS
    • Web

Screenshots/Videos

N/A — formatting-only lint fixes, no runtime or UI changes.

Formatting only: singlequotes, removed semicolons and trailing commas,
2-space indentation, standard function spacing. No logic changes.
@NicolasBonet
NicolasBonet requested a review from a team September 7, 2026 15:25
@melvin-bot
melvin-bot Bot requested review from MonilBhavsar and removed request for a team September 7, 2026 15:26
@MonilBhavsar
MonilBhavsar merged commit c94bdd9 into main Sep 7, 2026
5 of 6 checks passed
@os-botify

os-botify Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

🚀 Published to npm in 6.3.23 🎉

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.

2 participants