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

Enable eslint no-undef rule in JS compiler. NFC #23384

Merged
merged 1 commit into from
Jan 14, 2025

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Jan 13, 2025

This required making eslint aware of the settings globals which are used throughout the compiler.

Running this change revealed several legacy parseTools function that simply do not run due to references to undefined symbols (because of this we know that there are no active/current user of these functions).

@sbc100 sbc100 requested a review from kripken January 13, 2025 21:20
@sbc100 sbc100 force-pushed the eslint_improve branch 7 times, most recently from 2a0ffda to 5c555b9 Compare January 13, 2025 22:55
@sbc100 sbc100 requested review from dschuff and brendandahl January 13, 2025 22:55
eslint.config.mjs Outdated Show resolved Hide resolved
This required making eslint aware of the settings globals which are used
throughout the compiler.

Running this change revealed several legacy parseTools function that
simply do run due to references to undefined symbols (because of this we
know that there are not active/current user of these legacy function).
@sbc100 sbc100 merged commit 7aa70ae into emscripten-core:main Jan 14, 2025
2 of 9 checks passed
@sbc100 sbc100 deleted the eslint_improve branch January 14, 2025 20: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