Skip to content

Pull #18631: Add OptionalRulesRecipes #18629 #18627 #18625 #18622#18631

Closed
Pankraz76 wants to merge 1 commit into
checkstyle:masterfrom
Pankraz76:fix-CodeCleanup-refasterrules-OptionalRulesRecipes
Closed

Pull #18631: Add OptionalRulesRecipes #18629 #18627 #18625 #18622#18631
Pankraz76 wants to merge 1 commit into
checkstyle:masterfrom
Pankraz76:fix-CodeCleanup-refasterrules-OptionalRulesRecipes

Conversation

@Pankraz76

@Pankraz76 Pankraz76 commented Jan 12, 2026

Copy link
Copy Markdown

Pull #18631: Add OptionalRulesRecipes #18629 #18627 #18625 #18622

@Pankraz76 Pankraz76 changed the title Pull #18629: Add OptionalRulesRecipes #18629 #18627 #18625 #18622 Pull #18631: Add OptionalRulesRecipes #18629 #18627 #18625 #18622 Jan 12, 2026
@Pankraz76 Pankraz76 force-pushed the fix-CodeCleanup-refasterrules-OptionalRulesRecipes branch from a7892c9 to 88f5288 Compare January 12, 2026 21:39
@Pankraz76 Pankraz76 force-pushed the fix-CodeCleanup-refasterrules-OptionalRulesRecipes branch from 88f5288 to 96523bd Compare January 12, 2026 21:40
@Pankraz76 Pankraz76 marked this pull request as ready for review January 12, 2026 21:43

@romani romani left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Comment out this rule to make it clear it was considered, but disabled due to personal preferences


if (firstSentence.isPresent()) {
if (containsForbiddenFragment(firstSentence.get())) {
if (containsForbiddenFragment(firstSentence.orElseThrow())) {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I am not mentally ready for this update.
Let's disable this rule for now. New generation of maintainers might think differently, they can activate it.
Not now

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

i understand but just dont give so much attention.

looking into the numbers this argument makes not much sense, as we already have this all around 48 times:

image

so its already there what you dont like, meaning you already have the mental capacity for this. also its about adopting to new standards and evolve.

please reconsider.

If this would be the only once i would agree but currently the argument makes no sense, sorry.

@Pankraz76

Pankraz76 commented Jan 15, 2026

Copy link
Copy Markdown
Author

please merge and apply convention fix the gap. we have real issues but not such cosmetic stuff. just obey, its nothing new....

Pankraz76 pushed a commit to Pankraz76/checkstyle that referenced this pull request Jan 15, 2026
@Pankraz76

Copy link
Copy Markdown
Author

plz reply to merge or i make comment that you dont like 4 new items when there are already 48 items around.

its kind of nonsense wasting again.

lets try to stop starting and start finighing @romani

@romani romani left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

items:

Comment thread config/rewrite.yml Outdated
- tech.picnic.errorprone.refasterrules.MapRulesRecipes
- tech.picnic.errorprone.refasterrules.MicrometerRulesRecipes
- tech.picnic.errorprone.refasterrules.MockitoRulesRecipes
- tech.picnic.errorprone.refasterrules.OptionalRulesRecipes

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

disable it with comment "current maintainers do not like orElseThrow"

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

then have to revert all other.

with me only consequent changes going to happen.

might having to escalate this with other contributors to help out.

getPropertyVersionFromItsJavadoc(propertyJavadoc);

if (specifiedPropertyVersionInPropertyJavadoc.isPresent()) {
sinceVersion = specifiedPropertyVersionInPropertyJavadoc.get();

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

this actually a good trivial change having same behaviour but different code being finally aligned.

@Pankraz76 Pankraz76 force-pushed the fix-CodeCleanup-refasterrules-OptionalRulesRecipes branch from 373a5fd to c36a630 Compare January 18, 2026 09:59

@Pankraz76 Pankraz76 left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

kind of escalating, asking for feedback.

.filter(JavadocUtil::isJavadocComment)
.findFirst();
return javadoc.isPresent()
&& MATCH_INHERIT_DOC.matcher(javadoc.orElseThrow()).find();

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

this is kind of a joke to me.

Comment thread config/rewrite.yml Outdated
- tech.picnic.errorprone.refasterrules.MapRulesRecipes
- tech.picnic.errorprone.refasterrules.MicrometerRulesRecipes
- tech.picnic.errorprone.refasterrules.MockitoRulesRecipes
# current maintainer (romani) do not understand java properly; don't "like" orElseThrow.

@Pankraz76 Pankraz76 Jan 18, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

this is kind of a joke to me. making no arguments with numbers or content, but just arguing with obsolete opinion does not seem smart to me.

@elharo @gnodet @cstamas @rickie

Having to rely on this entity right again on the next PR. this change makes no sense to me.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

i would like to have a consistent way not some crazy random way. having 48 times orElseThrow but dont allow any further without any (valid) argument given?

@Pankraz76

Copy link
Copy Markdown
Author

sorry for going so extra, thanks. actually this the first commit i see from you.

Pankraz76 pushed a commit to Pankraz76/checkstyle that referenced this pull request Jan 25, 2026
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