Skip to content

fix: Issue misspelled warning only when it makes sense #2698

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

Merged
merged 3 commits into from
Jan 22, 2025

Conversation

slavek-kucera
Copy link
Contributor

No description provided.

@slavek-kucera slavek-kucera requested a review from ishche January 22, 2025 13:59
@slavek-kucera slavek-kucera marked this pull request as draft January 22, 2025 14:19
areaAWarning(ctx.getStart());
return getLocality(ctx.getStart())
.map(def -> addTreeNode(ctx, locality -> createParagraphWithNameNode(locality, ctx, def)))
.orElseGet(() -> visitChildren(ctx));
} else {
throwWarning(ctx.getStart());
Copy link
Contributor

Choose a reason for hiding this comment

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

maybe rename it to something related to misspell

@ishche
Copy link
Contributor

ishche commented Jan 22, 2025

Looks good

@slavek-kucera slavek-kucera marked this pull request as ready for review January 22, 2025 16:11
@slavek-kucera slavek-kucera requested a review from ishche January 22, 2025 16:11
@slavek-kucera slavek-kucera merged commit 367a412 into development Jan 22, 2025
18 checks passed
@slavek-kucera slavek-kucera deleted the fix_meaningless_warnings branch January 22, 2025 16:34
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.

2 participants