Skip to content

Comments

Added lint and formated all the files#56

Open
Maayanshani25 wants to merge 1 commit intovalkey-io:mainfrom
Maayanshani25:lint
Open

Added lint and formated all the files#56
Maayanshani25 wants to merge 1 commit intovalkey-io:mainfrom
Maayanshani25:lint

Conversation

@Maayanshani25
Copy link
Collaborator

@Maayanshani25 Maayanshani25 commented Jan 25, 2026

Followed the lint setup from valkey-glide and applied the same formatting rules here. Source
Added lint test to the CI.

When checking the pr focus only on /pom.xml and /.github/workflows/lint.yml

  • You have read the Spring Data contribution guidelines.
  • You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
  • You submit test cases (unit or integration tests) that back your changes.
  • You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

@Maayanshani25 Maayanshani25 force-pushed the lint branch 3 times, most recently from 4960a54 to db7ff13 Compare January 25, 2026 13:11
Signed-off-by: Maayan Shani <maayan.shani@mail.huji.ac.il>
@Maayanshani25 Maayanshani25 changed the title Add lint and format all the files Added lint and formated all the files Jan 25, 2026
@jeremyprime
Copy link
Collaborator

jeremyprime commented Jan 26, 2026

I'm wondering if we should align with Valkey formatting standards, or keep Spring formatting standards (like this PR is currently doing). We could make use of the Spring Data Build formatting here. I assume there would be much fewer changes if we stuck with the Spring Data formatting standards.

Should discuss with team to decide on what approach we want first.

pom.xml Outdated
<artifactId>maven-javadoc-plugin</artifactId>
<version>${maven-javadoc-plugin.version}</version>
</plugin>
<!-- Flatten plugin for Maven Central deployment -->
Copy link
Collaborator

Choose a reason for hiding this comment

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

The flatten plugin was removed, we need this. Make sure you have latest changes from main.

Comment on lines +285 to +292
<indent>
<tabs>true</tabs>
<spacesPerTab>2</spacesPerTab>
</indent>
<indent>
<spaces>true</spaces>
<spacesPerTab>4</spacesPerTab>
</indent>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Conflicting indentation rules, I assume it should just be 4.

<exclude>**/protobuf/**</exclude>
<exclude>**/target/**</exclude>
</excludes>
<importOrder/>
Copy link
Collaborator

@jeremyprime jeremyprime Jan 26, 2026

Choose a reason for hiding this comment

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

If we use Spring Data formatting, they have import order file we would reference here (could put a copy in this repo).

Comment on lines +280 to +284
<googleJavaFormat>
<version>${spotless-google-java-format.version}</version>
<reflowLongStrings>true</reflowLongStrings>
<groupArtifact>com.google.googlejavaformat:google-java-format</groupArtifact>
</googleJavaFormat>
Copy link
Collaborator

Choose a reason for hiding this comment

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

If we use Spring Data formatting, they have eclipse formatting file we would reference here (could put a copy in this repo).

@jeremyprime jeremyprime linked an issue Jan 26, 2026 that may be closed by this pull request
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.

Add Java formatting and lint checks

2 participants