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: spotless plugin (googleJavaFormat) #2706

Merged

Conversation

xstefank
Copy link
Collaborator

No description provided.

pom.xml Outdated
<java>
<googleJavaFormat>
<reflowLongStrings>true</reflowLongStrings>
<formatJavadoc>false</formatJavadoc>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why format javadoc is false?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

it was in the examples, but sure, why not

@csviri
Copy link
Collaborator

csviri commented Feb 27, 2025

@metacosm @xstefank I'm fine with basically both palantir and google format, not sure what are the major differences. If the palantir really has some major advantages over google.

@xstefank xstefank force-pushed the spotless-fix-2697-google-format branch from b68c59a to 0af0830 Compare February 27, 2025 09:05
@csviri
Copy link
Collaborator

csviri commented Feb 27, 2025

@metacosm @xstefank I'm fine with basically both palantir and google format, not sure what are the major differences. If the palantir really has some major advantages over google.

Given that google has bigger community we might want to choose that over palantir

@csviri
Copy link
Collaborator

csviri commented Feb 27, 2025

But if we could fix eclipse that would be the best :)

@xstefank xstefank force-pushed the spotless-fix-2697-google-format branch 2 times, most recently from d8a0ecc to 805f676 Compare February 27, 2025 09:47
@xstefank
Copy link
Collaborator Author

@csviri so are we going with this google-format then? :) Can I close the other PRs?

Copy link
Collaborator

@csviri csviri left a comment

Choose a reason for hiding this comment

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

I'm fine with this one, we should check if the links in the documentation are still correct, probably not, but that can be a separate PR.

@csviri
Copy link
Collaborator

csviri commented Feb 27, 2025

let's wait for @metacosm , what he thinks

@xstefank
Copy link
Collaborator Author

I updated links in this PR. Did I miss something?

@csviri
Copy link
Collaborator

csviri commented Feb 27, 2025

I updated links in this PR. Did I miss something?

In the /docs content, we reference source code in lot's of places, not sure - have to check - but in some places also lines, those are now probably outdated.
Probably we should always reference code by tags in the docs.

@xstefank
Copy link
Collaborator Author

@csviri I'll do a pass over docs in a follow up PR.

@csviri
Copy link
Collaborator

csviri commented Feb 28, 2025

@metacosm can we merge this? kinda blocks the work on other issues, if I want to avoid conflicts

@metacosm
Copy link
Collaborator

Going to check.

@csviri csviri force-pushed the spotless-fix-2697-google-format branch from 805f676 to 79376f8 Compare March 2, 2025 10:03
@metacosm
Copy link
Collaborator

metacosm commented Mar 3, 2025

Are there options we can tweak, like the line length?

@xstefank
Copy link
Collaborator Author

xstefank commented Mar 3, 2025

@metacosm
Copy link
Collaborator

metacosm commented Mar 3, 2025

OK, not too fond of the rather short line length but so be it…

@csviri csviri merged commit ba2dd39 into operator-framework:main Mar 3, 2025
20 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.

3 participants