[CI] Textlint: properly check for Java capitalization & more #3497
Conversation
This file contains 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
|
(A few more fixes are needed here, for other related issues. I'll submit those after my next meeting. Setting to Draft status for now.) |
chalin
force-pushed
the
chalin-im-textlint-dotjava-ok-2023-11-05
branch
from
868c783
to
6e1a98c
Compare
cartermp
approved these changes
Nov 5, 2023
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.
.java#3492terminologyto recognize and fix "Java" mis-capitalizations. In particular, it avoids reporting false positives:file.javaopentelemetry-javajava.util.List, as they might appear, e.g., in markdown link-textallowpattern.ymlfiles a markdown. This gives us better checking, with fewer false positives, especially for fields that contain markdowntagsallow patternPreview: e.g.,