chore: adjust eslint rules for if statements and fix new errors #201
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
antoniocapelo
requested review from
dragidavid,
lukad and
sandrina-p
and removed request for
dragidavid and
sandrina-p
antoniocapelo
force-pushed
the
devxp-2610-jsf-update-lint-to-follow-internal-guidelines
branch
from
a9fc6f2 to
ef32445
Compare
lukad
approved these changes
Jul 8, 2025
antoniocapelo
deleted the
devxp-2610-jsf-update-lint-to-follow-internal-guidelines
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following up on this discussion, I'm adjusting the eslint rules to force brackets after an
ifstatement (and fixed the errors that popped up)