Skip to content
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

Fix false positive in rules not counting imports in scope #592

Merged
merged 1 commit into from
Mar 11, 2024

Conversation

anderseknert
Copy link
Member

Fixes #590

That issue only mentions top-level-iteration, but I found the same behavior in use-some-for-output-vars, so this fixes that too.

Copy link
Member

@charlieegan3 charlieegan3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Fixes #590

That issue only mentions `top-level-iteration`, but I found
the same behavior in `use-some-for-output-vars`, so this fixes
that too.

Signed-off-by: Anders Eknert <anders@styra.com>
@anderseknert anderseknert merged commit fff72d9 into main Mar 11, 2024
3 checks passed
@anderseknert anderseknert deleted the top-level-iteration-import-fp branch March 11, 2024 14:03
srenatus pushed a commit to srenatus/regal that referenced this pull request Oct 1, 2024
Fixes StyraInc#590

That issue only mentions `top-level-iteration`, but I found
the same behavior in `use-some-for-output-vars`, so this fixes
that too.

Signed-off-by: Anders Eknert <anders@styra.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

False positive in top-level-iteration when a ref var is imported
2 participants