Apply spring-javaformat to GLIDE classes - #98
Merged
Conversation
Signed-off-by: Jeremy Parr-Pearson <jeremy.parr-pearson@improving.com>
xShinnRyuu
approved these changes
Jul 27, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Applies spring-javaformat conventions to all GLIDE-authored classes and adds the formatter plugin for ongoing style enforcement.
Closes #49
Changes
spring-javaformat-maven-plugin0.0.47 to root, examples, and performance pom.xmlvalkeyglidepackage classes (main + test) with spring-javaformat2025-presentfor all classes we authoredLimitations
Formatting is applied only to classes authored by this project (GLIDE driver, boot GLIDE config, examples, performance). Upstream-synced classes (Lettuce, Jedis, common) are intentionally left unformatted to avoid merge conflicts on future syncs.