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

Closes #311 - fix no_match_in_condition reports a warning even when the condition includes a valid match #368

Merged
merged 1 commit into from
Oct 31, 2024

Conversation

bormilan
Copy link
Contributor

@bormilan bormilan commented Oct 30, 2024

Description

My idea was to check only the "first layer of children" of the case type Node.
And I added the type block too.

Closes #311;.

@elbrujohalcon
Copy link
Member

I'll let @paulo-ferraz-oliveira review, too... but from my perspective, this is 100% mergeable.

@elbrujohalcon elbrujohalcon changed the title fix no_match_in_condition Closes #311 - fix no_match_in_condition reports a warning even when the condition includes a valid match Oct 31, 2024
@elbrujohalcon elbrujohalcon merged commit df9fe91 into inaka:main Oct 31, 2024
7 checks passed
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.

no_match_in_condition reports a warning even when the condition includes a valid match
2 participants