-
Notifications
You must be signed in to change notification settings - Fork 1k
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
DRAFT: Code formatting using spotless in Phoenix #1995
Conversation
This code can be reviewed, just that not ready for merge. Need to add JIRA title and also decide whether should go as one commit or multi commit. |
There was already a DISCUSS thread on this back in Januray 2023, but nothing happened. I think that this is visible and high impact enough to warrant another [DISCUSS] thread. I think we should do this, BTW. |
@@ -167,6 +167,7 @@ | |||
<exec-maven-plugin.version>3.1.1</exec-maven-plugin.version> | |||
<maven-checkstyle-plugin.version>3.3.0</maven-checkstyle-plugin.version> | |||
<mvel2.version>2.5.2.Final</mvel2.version> | |||
<spotless.version>2.27.2</spotless.version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a pretty old version (from 2022). Is there a reason you're not using the latest? (2.43.0)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes you are right. I just kept this in sync with hbase but yes let me bump into hbase codebase as well and move to the latest one over here as well.
Thank you so much for picking this up. I just stumbled upon the previous PR, Jira issue and the previous mailing list thread. I do appreciate the work a lot and can try to help out where I can. I also appreciate that you split the PR up in multiple commits. |
Sure @stoty Thank you for the reference. Let me chime into DISCUSS thread and put up what we plan to do here.
Thank you @lfrancke for bringing this up again on DISCUSS, and for pointing out the JIRA for previous issue.
Sure will be great if you can help with reviews. Will let you know if anything else if needed.
I plan to raise 3 PRs . This PR was just to demo the level of inconsistency we have in the codebase and seek feedback. Let me create appropriate JIRAs and raise 3 distinct PRs.
Also need to break the "machinery" part into tasks: task 1 and task 3 as we may want to add to pre-commit only after all issues are fixed with task2. This way we can have ease of backporting as well since task 2 generated code may differ for all branches. |
Excellent, in that case I just misread. Thank you! The plan makes sense to me. |
work superceded at #2023 |
This PR currently has 3 commits, each of which do independent tasks as follows:
We could create 3 JIRA sub tasks and do each commit one at a time for ease of backporting.
TODO: Raise JIRAs as needed