Skip to content

Comments

Migrated from JSHint to ESLint#3836

Open
Nishthajain7 wants to merge 1 commit intoprocessing:develop-codemirror-v6from
Nishthajain7:migarte-to-eslint
Open

Migrated from JSHint to ESLint#3836
Nishthajain7 wants to merge 1 commit intoprocessing:develop-codemirror-v6from
Nishthajain7:migarte-to-eslint

Conversation

@Nishthajain7
Copy link

Fixes #1540

Changes: Updated the preprocessing lint step to use ESLint instead of JSHint.

I have verified that this pull request:

  • has no linting errors (npm run lint)
  • has no test errors (npm run test)
  • has no typecheck errors (npm run typecheck)
  • is from a uniquely-named feature branch and is up to date with the develop branch.
  • is descriptively named and links to an issue number, i.e. Fixes #123
  • meets the standards outlined in the accessibility guidelines

@welcome
Copy link

welcome bot commented Feb 2, 2026

🎉 Thanks for opening this pull request! Please check out our contributing guidelines if you haven't already.

@khanniie
Copy link
Member

Hi! Thank you so much for the contribution! If this is regarding the codemirror 5 to 6 migration, the subissue we published was actually regarding the js linter used within the Editor/stateUtils.js file. I do think the approach is correct, it would be great if you could move the changes to that file!

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