fix: eslint warnings above hardcoded threshold#14799
Merged
iankhou merged 1 commit intogen2-migrationfrom Apr 23, 2026
Merged
Conversation
iliapolo
approved these changes
Apr 23, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of changes
In the
_lintstep of ourAmplifyCLI-E2E-TestingCodeBuild job, we runyarn lint-check, which runsyarn eslint . --ext .js,.jsx,.ts,.tsx --max-warnings=750.With the inclusion of Gen 2 Migration changes, we are at 999 warnings, which is beyond the existing threshold. This change modifies the value passed to
--max-warningsto 1500.Issue #, if available
Description of how you validated changes
Checklist
yarn testpassesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.