# Description
This PR integrates the prettier check in the github workflow to ensure
the code respects the correct formatting standards
Fixes#177馃
---------
Co-authored-by: Ivan Shymko <vana.shimko@gmail.com>
# Description
This pull request introduces a new ESLint configuration file,
`eslint.config.mjs` to standardize code quality and style across the
project.
Here's a summary of the key changes:
- ESLint Setup with TypeScript and Prettier Integration: The
configuration now leverages @eslint/js and typescript-eslint for linting
of TypeScript code. eslint-config-prettier is included to disable any
ESLint rules that might conflict with Prettier's formatting, which will
be included in a new PR.
- Ignored Files: The dist/ and node_modules/ directories are explicitly
ignored to prevent linting of generated output and third-party
dependencies.
Custom Rule Adjustments:
- @typescript-eslint/no-explicit-any is turned off to allow the use of
the any type where necessary.
- @typescript-eslint/no-unused-vars is configured to ignore unused
arguments and caught errors that are prefixed with an underscore (_).
This is a common pattern to signal intentional unused variables.
Test File Specific Rules:
- @typescript-eslint/no-unused-expressions is turned off to accommodate
testing libraries like Chai, which often use expression-based
assertions.
- @typescript-eslint/no-unsafe-function-type is turned off to allow more
flexible function type usage within test contexts.
Node.js Global Variables: The configuration now includes globals.node to
correctly recognize Node.js global variables, preventing false positives
for undefined variables in Node.js environments.
The changes in other files in this PR are necessary for the linter
checks to pass. They involve mainly the removal of unused parameters.
Re #177馃