-
Notifications
You must be signed in to change notification settings - Fork 0
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
Experiment: convert eslint to flat config #582
Comments
sergei-maertens
added a commit
that referenced
this issue
Jan 6, 2025
CRA ships with a default ESLint config, which is overridden in the project to disable some bits. ESLint is moving towards flat config, and CRA (unmaintained) is not compatible with it, so we set up our own flows. The envvar disables the CRA integration in react-scripts, as it does not pick up the new config file. The pre-commit checks and CI pipeline ensure that code is properly linted before being committed. We also use the shared config from Maykin for consistency across projects.
sergei-maertens
added a commit
that referenced
this issue
Jan 6, 2025
sergei-maertens
added a commit
that referenced
this issue
Jan 6, 2025
Addressed the linter errors to minimize the impact on the project. Some lines are ignored because they are valid and consistent in the project, but ignoring the rule as a whole would allow other mistakes to fall through/go undetected.
sergei-maertens
added a commit
that referenced
this issue
Jan 6, 2025
CRA ships with a default ESLint config, which is overridden in the project to disable some bits. ESLint is moving towards flat config, and CRA (unmaintained) is not compatible with it, so we set up our own flows. The envvar disables the CRA integration in react-scripts, as it does not pick up the new config file. The pre-commit checks and CI pipeline ensure that code is properly linted before being committed. We also use the shared config from Maykin for consistency across projects.
sergei-maertens
added a commit
that referenced
this issue
Jan 6, 2025
sergei-maertens
added a commit
that referenced
this issue
Jan 6, 2025
Addressed the linter errors to minimize the impact on the project. Some lines are ignored because they are valid and consistent in the project, but ignoring the rule as a whole would allow other mistakes to fall through/go undetected.
sergei-maertens
added a commit
that referenced
this issue
Jan 6, 2025
CRA ships with a default ESLint config, which is overridden in the project to disable some bits. ESLint is moving towards flat config, and CRA (unmaintained) is not compatible with it, so we set up our own flows. The envvar disables the CRA integration in react-scripts, as it does not pick up the new config file. The pre-commit checks and CI pipeline ensure that code is properly linted before being committed. We also use the shared config from Maykin for consistency across projects.
sergei-maertens
added a commit
that referenced
this issue
Jan 6, 2025
sergei-maertens
added a commit
that referenced
this issue
Jan 6, 2025
Addressed the linter errors to minimize the impact on the project. Some lines are ignored because they are valid and consistent in the project, but ignoring the rule as a whole would allow other mistakes to fall through/go undetected.
sergei-maertens
added a commit
that referenced
this issue
Jan 7, 2025
CRA ships with a default ESLint config, which is overridden in the project to disable some bits. ESLint is moving towards flat config, and CRA (unmaintained) is not compatible with it, so we set up our own flows. The envvar disables the CRA integration in react-scripts, as it does not pick up the new config file. The pre-commit checks and CI pipeline ensure that code is properly linted before being committed. We also use the shared config from Maykin for consistency across projects.
sergei-maertens
added a commit
that referenced
this issue
Jan 7, 2025
sergei-maertens
added a commit
that referenced
this issue
Jan 7, 2025
Addressed the linter errors to minimize the impact on the project. Some lines are ignored because they are valid and consistent in the project, but ignoring the rule as a whole would allow other mistakes to fall through/go undetected.
svenvandescheur
pushed a commit
that referenced
this issue
Jan 7, 2025
CRA ships with a default ESLint config, which is overridden in the project to disable some bits. ESLint is moving towards flat config, and CRA (unmaintained) is not compatible with it, so we set up our own flows. The envvar disables the CRA integration in react-scripts, as it does not pick up the new config file. The pre-commit checks and CI pipeline ensure that code is properly linted before being committed. We also use the shared config from Maykin for consistency across projects.
svenvandescheur
pushed a commit
that referenced
this issue
Jan 7, 2025
svenvandescheur
pushed a commit
that referenced
this issue
Jan 7, 2025
Addressed the linter errors to minimize the impact on the project. Some lines are ignored because they are valid and consistent in the project, but ignoring the rule as a whole would allow other mistakes to fall through/go undetected.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following open-formulieren/open-forms-sdk#724 - let's see if we can establish a common baseline config to share across maykin projects.
The text was updated successfully, but these errors were encountered: