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

Configure eslint rules #508

Merged
merged 6 commits into from
Jul 13, 2023
Merged

Configure eslint rules #508

merged 6 commits into from
Jul 13, 2023

Conversation

bertschneider
Copy link
Contributor

The current test files show that file specific eslint rule configurations got out of hand.

eslint rules should be configured according to the project’s needs. E.g. the ones which are normally disabled on a per file basis can safely be disabled globally.

@bertschneider bertschneider force-pushed the FUZZ-754_configure_eslint_rules branch from d6f5c75 to 602ea7e Compare July 12, 2023 14:17
@bertschneider bertschneider requested a review from a team July 12, 2023 14:31
require is used in many tests and even in some hooks, and is should not
be problematic.
Introduce Jest globals to not disable no-undef rule all the time.
The JavaScript interop requires to disable TypeScript checks at some
places. Disable this rule for now.
As Jest fuzz functions require the data parameter, even if not used,
disable the no-unused-vars check globally.
@bertschneider bertschneider force-pushed the FUZZ-754_configure_eslint_rules branch from 602ea7e to eba94c5 Compare July 13, 2023 15:14
@bertschneider bertschneider enabled auto-merge (rebase) July 13, 2023 15:14
@bertschneider bertschneider merged commit 76aeddb into main Jul 13, 2023
6 checks passed
@bertschneider bertschneider deleted the FUZZ-754_configure_eslint_rules branch July 13, 2023 15:31
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.

None yet

2 participants