chore: suppress no-implied-eval warnings in codegen tests#156
Merged
FredKSchott merged 1 commit intomainfrom Feb 27, 2026
Merged
chore: suppress no-implied-eval warnings in codegen tests#156FredKSchott merged 1 commit intomainfrom
FredKSchott merged 1 commit intomainfrom
Conversation
These tests intentionally use new Function() to evaluate generated middleware codegen output. Add eslint-disable-next-line comments to fix --deny-warnings CI failures.
commit: |
Collaborator
Author
|
self-approving, this just adds linter comments (no code changes) and fixes failing CI on main |
|
southpolesteve
pushed a commit
that referenced
this pull request
Feb 27, 2026
Co-authored-by: ask-bonk[bot] <ask-bonk[bot]@users.noreply.github.com>
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
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.
Summary
eslint-disable-next-line no-implied-evalto 3new Function()calls intests/shims.test.ts