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

Polish #1269

Merged
merged 5 commits into from
Jun 14, 2024
Merged

Polish #1269

merged 5 commits into from
Jun 14, 2024

Conversation

rajadilipkolli
Copy link
Owner

@rajadilipkolli rajadilipkolli commented Jun 14, 2024

Summary by CodeRabbit

  • Style

    • Made variables final for immutability in multiple files.
    • Updated log message formats for better clarity and readability.
    • Improved comment clarity in configuration files.
  • Refactor

    • Refactored methods to use more concise syntax and improve readability.
    • Updated method signatures to handle Optional values more efficiently.
    • Switched to using Lombok annotations for automatic getter generation.
  • Documentation

    • Updated README files to correct grammatical errors and clarify instructions.
    • Modified links to sample code in documentation for better navigation.
  • Tests

    • Refactored test methods for better code organization and readability.
    • Ensured test variables are declared as final for consistency.

@rajadilipkolli rajadilipkolli self-assigned this Jun 14, 2024
Copy link
Contributor

coderabbitai bot commented Jun 14, 2024

Warning

Rate limit exceeded

@rajadilipkolli has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 26 minutes and 2 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 84a59b4 and 49a79a7.

Walkthrough

The recent changes span various projects, focusing on simplifications, immutability enhancements, code clarity improvements, and method optimizations. These updates ensure more maintainable code, reduced redundancy, and better adherence to coding standards without significantly altering functionality.

Changes

File/Directory Path Change Summary
.../architecture/CustomConditions.java Simplified instantiation of ArchCondition instances using diamond operators.
.../chaosmonkey/gatling/CustomerRequestSimulation.java Declared variables httpProtocol, feeder, and scn as final.
.../grafana/provisioning/datasources/datasource.yml Updated comment for clarity regarding datasource insertion/updating based on availability.
.../mongoes/web/service/SearchService.java Made aggregationFunction variable final.
.../elasticsearch/repository/RestaurantESRepositoryIntegrationTest.java Modified access to Restaurant objects using getFirst() method in test methods.
.../opensearch/config/Initializer.java Updated a log message to include properties.getCors().
.../opensearch/services/RestaurantSearchService.java Declared aggregationFunction as final.
.../common/ContainersConfig.java Made openSearchContainer field final and used method reference for openSearchContainer::getHttpHostAddress.
.../web/controllers/UserControllerTest.java Removed unnecessary semicolons after method invocations in tests.
.../docker-compose-app.yml Changed port mapping syntax for a service.
.../redis/config/CacheConfig.java Updated log message format using string interpolation.
.../graphql/entities/Post.java Removed FetchType.LAZY attribute from the @OneToOne annotation for the details field.
.../graphql-webflux/.../GlobalErrorWebExceptionHandler.java Removed methods and imports related to error handling and response rendering.
.../graphql-webmvc/.../LocalDateTimeScalar.java Refactored parseValue method for readability using a switch statement with pattern matching.
.../graphql-webmvc/.../AuthorService.java Added import for Objects and used Objects.requireNonNull in the saveAuthor method.
.../graphql-webmvc/.../PostDetailsService.java updatePostDetails now returns an Optional<PostDetailsInfo>.
.../graphql-webmvc/.../PostDetailsController.java Refactored control flow in updatePostDetails for efficiency in handling Optional values.
.../graphql-webmvc/.../PostDetailsEntityControllerTest.java Updated method return value to handle Optional.
.../graphql-webmvc/.../PostEntityControllerTest.java Changed postResponseList field to an immutable list.
.../httpClients/README.md Updated links to sample code paths for Spring Boot integrations.
.../custom/sequence/web/api/CustomerAPI.java Removed empty parameter descriptions and adjusted annotations.
.../custom/sequence/web/controllers/OrderControllerTest.java Added import for @NotNull; refactored method to use a private retrieval method.
.../envers/.../datasource.yml Improved comment clarity regarding datasource insertion/updating.
.../envers/src/test/java/.../ApplicationIntegrationTest.java Updated assertion structure in the updateIncreasesRevisionNumber() method.
.../hibernatecache/.../GlobalExceptionHandler.java Used Objects.requireNonNull for fieldError.getRejectedValue() in exception handling.
.../hibernatecache/.../CustomerControllerTest.java Removed setUp() method and refactored getCustomerResponses() method.
.../hibernatecache/.../OrderControllerTest.java Made the customer variable final.
.../jpa-locks/README.md Emphasized the trade-off between consistency and performance when selecting isolation and propagation levels.
.../readreplica/.../RoutingDataSource.java Removed auto-generated SQL exception handling and logging methods.
.../multitenancy/README.md Corrected grammatical error in explaining multitenancy approaches.
.../multidatasource/.../PrimaryDataSourceConfiguration.java Added generic types <String> to MultiTenantConnectionProvider and CurrentTenantIdentifierResolver.
.../multidatasource/.../SecondaryDataSourceConfiguration.java Added generic types <String> to MultiTenantConnectionProvider and CurrentTenantIdentifierResolver.
.../multidatasource/.../TenantIdentifierResolver.java Specified String type parameter for CurrentTenantIdentifierResolver.
.../multidatasource/.../TenantRoutingDatasource.java Removed methods isWrapperFor, unwrap, and getParentLogger.
.../multidatasource/.../DatabaseType.java Added Lombok's @Getter annotation and changed the constructor's visibility to package-private.
.../multitenancy-db/.../TenantIdentifierResolver.java Specified String type parameter for CurrentTenantIdentifierResolver.

Poem

In the world of code so bright,
Changes came with morning light,
Variables now forever still,
With final touches, quiescent thrill.
Comments clear as crystal streams,
Refactored methods, coder dreams.
Celebrate this code refined,
In joyful bytes, our work aligned. 🚀🐇


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 11

Outside diff range and nitpick comments (9)
jpa/boot-data-envers/config/grafana/provisioning/datasources/datasource.yml (1)

Line range hint 17-17: Add a newline at the end of file to adhere to POSIX standards.

+ 
Tools
yamllint

[error] 7-7: line too long (84 > 80 characters) (line-length)

graphql/boot-graphql-webmvc/config/grafana/provisioning/datasources/datasource.yml (1)

Line range hint 19-19: Add a newline character at the end of the file to conform to POSIX standards and avoid potential issues with tools that expect it.

+ 
Tools
yamllint

[error] 8-8: line too long (84 > 80 characters) (line-length)

jpa/multitenancy/README.md (1)

Line range hint 3-3: Adjust the indentation of unordered list items to enhance readability and adhere to Markdown conventions.

- - MultiTenancy is a feature of JPA that allows you...
+ - MultiTenancy is a feature of JPA that allows you...
- - This allows you to create a single entity class...
+ - This allows you to create a single entity class...

Also applies to: 5-5

Tools
Markdownlint

5-5: Expected: 0; Actual: 1 (MD007, ul-indent)
Unordered list indentation


10-10: null (MD028, no-blanks-blockquote)
Blank line inside blockquote

boot-mongodb-elasticsearch/config/grafana/provisioning/datasources/datasource.yml (1)

Line range hint 39-39: Correct the indentation to match the YAML structure, expected 4 but found 5.

Tools
yamllint

[error] 9-9: line too long (84 > 80 characters) (line-length)


[error] 12-12: wrong indentation: expected 2 but found 0 (indentation)

boot-togglz-sample/config/grafana/provisioning/datasources/datasource.yml (1)

Line range hint 39-39: Adjust the indentation of jsonData field to maintain consistency.

    jsonData:
Tools
yamllint

[error] 9-9: line too long (84 > 80 characters) (line-length)


[error] 12-12: wrong indentation: expected 2 but found 0 (indentation)

jpa/boot-jpa-locks/README.md (1)

Line range hint 17-54: Several markdown formatting issues detected:

- ### Format code
+ ## Format code
- ### Run tests
+ ## Run tests
- ### Run locally
+ ## Run locally
- ### Using Testcontainers at Development Time
+ ## Using Testcontainers at Development Time
- ### Useful Links
+ ## Useful Links

Correct these to maintain consistent heading levels.

Tools
LanguageTool

[style] ~19-~19: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing. (REP_NEED_TO_VB)
Context: ...k, use PROPAGATION_REQUIRED. If you need to isolate some operations from your curre...

techstack.md (3)

Line range hint 460-460: The phrase "Open source packages" should be hyphenated to "Open-source packages" when used as a compound adjective modifying "packages". This will improve the grammatical correctness of the documentation.

- Open source packages
+ Open-source packages

Line range hint 469-482: Several links in the document are empty, which can confuse users or lead to a poor user experience. It is recommended to either remove these links or provide the correct URLs.


Line range hint 99-462: Many images in the document are missing alternative text descriptions (alt text). Adding alt text is crucial for accessibility as it describes the images to users who are visually impaired. Please add appropriate alt texts to all images.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c77726f and 44e4b02.

Files selected for processing (53)
  • boot-api-archunit-sample/src/test/java/com/example/archunit/architecture/CustomConditions.java (3 hunks)
  • boot-choas-monkey/src/test/java/com/example/choasmonkey/gatling/CustomerRequestSimulation.java (1 hunks)
  • boot-mongodb-elasticsearch/config/grafana/provisioning/datasources/datasource.yml (1 hunks)
  • boot-mongodb-elasticsearch/src/main/java/com/example/mongoes/web/service/SearchService.java (1 hunks)
  • boot-mongodb-elasticsearch/src/test/java/com/example/mongoes/elasticsearch/repository/RestaurantESRepositoryIntegrationTest.java (11 hunks)
  • boot-opensearch-sample/src/main/java/com/example/opensearch/config/Initializer.java (1 hunks)
  • boot-opensearch-sample/src/main/java/com/example/opensearch/services/RestaurantSearchService.java (1 hunks)
  • boot-opensearch-sample/src/test/java/com/example/opensearch/common/ContainersConfig.java (2 hunks)
  • boot-rest-docs-sample/src/test/java/com/example/restdocs/web/controllers/UserControllerTest.java (2 hunks)
  • boot-strategy-plugin/docker-compose-app.yml (1 hunks)
  • boot-togglz-sample/config/grafana/provisioning/datasources/datasource.yml (1 hunks)
  • boot-ultimate-redis/src/main/java/com/example/ultimateredis/config/CacheConfig.java (1 hunks)
  • graphql/boot-graphql-querydsl/src/main/java/com/example/graphql/querydsl/entities/Post.java (1 hunks)
  • graphql/boot-graphql-webflux/src/main/java/com/example/graphql/exception/GlobalErrorWebExceptionHandler.java (2 hunks)
  • graphql/boot-graphql-webmvc/config/grafana/provisioning/datasources/datasource.yml (1 hunks)
  • graphql/boot-graphql-webmvc/src/main/java/com/example/graphql/config/graphql/LocalDateTimeScalar.java (1 hunks)
  • graphql/boot-graphql-webmvc/src/main/java/com/example/graphql/services/AuthorService.java (2 hunks)
  • graphql/boot-graphql-webmvc/src/main/java/com/example/graphql/services/PostDetailsService.java (1 hunks)
  • graphql/boot-graphql-webmvc/src/main/java/com/example/graphql/web/controllers/PostDetailsController.java (2 hunks)
  • graphql/boot-graphql-webmvc/src/test/java/com/example/graphql/web/controllers/PostDetailsEntityControllerTest.java (1 hunks)
  • graphql/boot-graphql-webmvc/src/test/java/com/example/graphql/web/controllers/PostEntityControllerTest.java (1 hunks)
  • httpClients/README.md (1 hunks)
  • httpClients/boot-http-proxy/src/test/java/com/example/rest/proxy/web/controllers/PostControllerTest.java (2 hunks)
  • httpClients/boot-web-client-mvc/src/main/java/com/example/rest/webclient/exception/GlobalExceptionHandler.java (1 hunks)
  • httpClients/boot-web-client-webflux/src/test/java/com/example/rest/webclient/web/controllers/PostControllerTest.java (1 hunks)
  • jpa/boot-data-customsequence/src/main/java/com/example/custom/sequence/web/api/CustomerAPI.java (3 hunks)
  • jpa/boot-data-customsequence/src/test/java/com/example/custom/sequence/web/controllers/OrderControllerTest.java (3 hunks)
  • jpa/boot-data-envers/config/grafana/provisioning/datasources/datasource.yml (1 hunks)
  • jpa/boot-data-envers/src/test/java/com/example/envers/ApplicationIntegrationTest.java (1 hunks)
  • jpa/boot-hibernate2ndlevelcache-sample/src/main/java/com/example/hibernatecache/config/GlobalExceptionHandler.java (1 hunks)
  • jpa/boot-hibernate2ndlevelcache-sample/src/test/java/com/example/hibernatecache/TestApplication.java (2 hunks)
  • jpa/boot-hibernate2ndlevelcache-sample/src/test/java/com/example/hibernatecache/web/controllers/CustomerControllerTest.java (3 hunks)
  • jpa/boot-hibernate2ndlevelcache-sample/src/test/java/com/example/hibernatecache/web/controllers/OrderControllerTest.java (1 hunks)
  • jpa/boot-jpa-locks/README.md (1 hunks)
  • jpa/boot-read-replica-postgresql/src/main/java/com/example/demo/readreplica/config/routing/RoutingDataSource.java (1 hunks)
  • jpa/multitenancy/README.md (1 hunks)
  • jpa/multitenancy/multidatasource-multitenancy/src/main/java/com/example/multitenancy/config/multidatasource/PrimaryDataSourceConfiguration.java (1 hunks)
  • jpa/multitenancy/multidatasource-multitenancy/src/main/java/com/example/multitenancy/config/multidatasource/SecondaryDataSourceConfiguration.java (1 hunks)
  • jpa/multitenancy/multidatasource-multitenancy/src/main/java/com/example/multitenancy/config/multitenant/TenantIdentifierResolver.java (1 hunks)
  • jpa/multitenancy/multidatasource-multitenancy/src/main/java/com/example/multitenancy/config/multitenant/TenantRoutingDatasource.java (1 hunks)
  • jpa/multitenancy/multidatasource-multitenancy/src/main/java/com/example/multitenancy/utils/DatabaseType.java (2 hunks)
  • jpa/multitenancy/multitenancy-db/src/main/java/com/example/multitenancy/db/config/multitenant/TenantIdentifierResolver.java (1 hunks)
  • jpa/multitenancy/multitenancy-db/src/main/java/com/example/multitenancy/db/config/multitenant/TenantRoutingDatasource.java (1 hunks)
  • jpa/multitenancy/partition/src/main/java/com/example/multitenancy/partition/config/tenant/TenantIdentifierResolver.java (1 hunks)
  • jpa/multitenancy/partition/src/test/java/com/example/multitenancy/partition/ApplicationIntegrationTest.java (1 hunks)
  • jpa/multitenancy/schema/src/main/java/com/example/multitenancy/schema/config/multitenancy/TenantIdentifierResolver.java (1 hunks)
  • jpa/multitenancy/schema/src/main/java/com/example/multitenancy/schema/utils/TenantNameType.java (1 hunks)
  • r2dbc/boot-jooq-r2dbc-sample/src/main/java/com/example/jooq/r2dbc/config/Initializer.java (1 hunks)
  • r2dbc/boot-jooq-r2dbc-sample/src/main/java/com/example/jooq/r2dbc/config/JooqConfiguration.java (2 hunks)
  • r2dbc/boot-jooq-r2dbc-sample/src/main/java/com/example/jooq/r2dbc/entities/Status.java (1 hunks)
  • r2dbc/boot-r2dbc-sample/src/test/java/com/example/bootr2dbc/web/controllers/ReactiveCommentsControllerTest.java (1 hunks)
  • scheduler/boot-scheduler-quartz/src/main/java/com/scheduler/quartz/model/common/Message.java (2 hunks)
  • techstack.md (1 hunks)
Files skipped from review due to trivial changes (17)
  • boot-api-archunit-sample/src/test/java/com/example/archunit/architecture/CustomConditions.java
  • boot-choas-monkey/src/test/java/com/example/choasmonkey/gatling/CustomerRequestSimulation.java
  • boot-mongodb-elasticsearch/src/main/java/com/example/mongoes/web/service/SearchService.java
  • boot-rest-docs-sample/src/test/java/com/example/restdocs/web/controllers/UserControllerTest.java
  • boot-ultimate-redis/src/main/java/com/example/ultimateredis/config/CacheConfig.java
  • graphql/boot-graphql-webmvc/src/test/java/com/example/graphql/web/controllers/PostEntityControllerTest.java
  • httpClients/boot-http-proxy/src/test/java/com/example/rest/proxy/web/controllers/PostControllerTest.java
  • httpClients/boot-web-client-webflux/src/test/java/com/example/rest/webclient/web/controllers/PostControllerTest.java
  • jpa/boot-data-customsequence/src/main/java/com/example/custom/sequence/web/api/CustomerAPI.java
  • jpa/boot-data-envers/src/test/java/com/example/envers/ApplicationIntegrationTest.java
  • jpa/boot-hibernate2ndlevelcache-sample/src/test/java/com/example/hibernatecache/web/controllers/CustomerControllerTest.java
  • jpa/boot-hibernate2ndlevelcache-sample/src/test/java/com/example/hibernatecache/web/controllers/OrderControllerTest.java
  • jpa/boot-read-replica-postgresql/src/main/java/com/example/demo/readreplica/config/routing/RoutingDataSource.java
  • jpa/multitenancy/multidatasource-multitenancy/src/main/java/com/example/multitenancy/config/multitenant/TenantRoutingDatasource.java
  • jpa/multitenancy/multitenancy-db/src/main/java/com/example/multitenancy/db/config/multitenant/TenantRoutingDatasource.java
  • r2dbc/boot-jooq-r2dbc-sample/src/main/java/com/example/jooq/r2dbc/config/Initializer.java
  • r2dbc/boot-r2dbc-sample/src/test/java/com/example/bootr2dbc/web/controllers/ReactiveCommentsControllerTest.java
Additional context used
yamllint
jpa/boot-data-envers/config/grafana/provisioning/datasources/datasource.yml

[error] 7-7: line too long (84 > 80 characters) (line-length)


[error] 17-17: no new line character at the end of file (new-line-at-end-of-file)

graphql/boot-graphql-webmvc/config/grafana/provisioning/datasources/datasource.yml

[error] 8-8: line too long (84 > 80 characters) (line-length)


[error] 19-19: no new line character at the end of file (new-line-at-end-of-file)

boot-mongodb-elasticsearch/config/grafana/provisioning/datasources/datasource.yml

[error] 9-9: line too long (84 > 80 characters) (line-length)


[error] 12-12: wrong indentation: expected 2 but found 0 (indentation)


[error] 39-39: wrong indentation: expected 4 but found 5 (indentation)

boot-togglz-sample/config/grafana/provisioning/datasources/datasource.yml

[error] 9-9: line too long (84 > 80 characters) (line-length)


[error] 12-12: wrong indentation: expected 2 but found 0 (indentation)


[error] 39-39: wrong indentation: expected 4 but found 5 (indentation)

boot-strategy-plugin/docker-compose-app.yml

[error] 5-5: line too long (92 > 80 characters) (line-length)


[error] 9-9: trailing spaces (trailing-spaces)


[error] 20-20: too many spaces inside brackets (brackets)


[error] 20-20: too many spaces inside brackets (brackets)


[error] 31-31: line too long (93 > 80 characters) (line-length)


[error] 37-37: too many spaces inside brackets (brackets)


[error] 37-37: too many spaces inside brackets (brackets)


[error] 39-39: line too long (106 > 80 characters) (line-length)


[error] 56-56: line too long (93 > 80 characters) (line-length)


[error] 82-82: line too long (86 > 80 characters) (line-length)


[error] 83-83: too many blank lines (1 > 0) (empty-lines)

Markdownlint
jpa/multitenancy/README.md

3-3: Expected: 0; Actual: 1 (MD007, ul-indent)
Unordered list indentation


5-5: Expected: 0; Actual: 1 (MD007, ul-indent)
Unordered list indentation


10-10: null (MD028, no-blanks-blockquote)
Blank line inside blockquote


12-12: null (MD028, no-blanks-blockquote)
Blank line inside blockquote

httpClients/README.md

4-4: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


10-10: Column: 65 (MD010, no-hard-tabs)
Hard tabs

jpa/boot-jpa-locks/README.md

24-24: Expected: h2; Actual: h3 (MD001, heading-increment)
Heading levels should only increment by one level at a time


23-23: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


51-51: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


27-27: null (MD014, commands-show-output)
Dollar signs used before commands without showing output


33-33: null (MD014, commands-show-output)
Dollar signs used before commands without showing output


39-39: null (MD014, commands-show-output)
Dollar signs used before commands without showing output


40-40: null (MD014, commands-show-output)
Dollar signs used before commands without showing output


43-43: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


52-52: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


53-53: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


53-53: null (MD034, no-bare-urls)
Bare URL used


54-54: null (MD034, no-bare-urls)
Bare URL used

techstack.md

459-459: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


98-98: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


105-105: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


134-134: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


179-179: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


290-290: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


401-401: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


414-414: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


469-469: null (MD042, no-empty-links)
No empty links


470-470: null (MD042, no-empty-links)
No empty links


481-481: null (MD042, no-empty-links)
No empty links


482-482: null (MD042, no-empty-links)
No empty links


497-497: null (MD042, no-empty-links)
No empty links


99-99: null (MD045, no-alt-text)
Images should have alternate text (alt text)


99-99: null (MD045, no-alt-text)
Images should have alternate text (alt text)


105-105: null (MD045, no-alt-text)
Images should have alternate text (alt text)


134-134: null (MD045, no-alt-text)
Images should have alternate text (alt text)


179-179: null (MD045, no-alt-text)
Images should have alternate text (alt text)


290-290: null (MD045, no-alt-text)
Images should have alternate text (alt text)


401-401: null (MD045, no-alt-text)
Images should have alternate text (alt text)


460-460: null (MD045, no-alt-text)
Images should have alternate text (alt text)


462-462: null (MD045, no-alt-text)
Images should have alternate text (alt text)

LanguageTool
httpClients/README.md

[uncategorized] ~8-~8: This verb does not appear to agree with the subject. Consider using a different form. (AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
Context: ...ing HTTP requests. The following table list all sample codes related to the spring ...

jpa/boot-jpa-locks/README.md

[style] ~19-~19: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing. (REP_NEED_TO_VB)
Context: ...k, use PROPAGATION_REQUIRED. If you need to isolate some operations from your curre...

techstack.md

[uncategorized] ~460-~460: If this is a compound adjective that modifies the following noun, use a hyphen. (EN_COMPOUND_ADJECTIVE_INTERNAL)
Context: ...https://img.stackshare.io/group.svg' /> Open source packages (38) ## <img width='24' ...

Additional comments not posted (35)
r2dbc/boot-jooq-r2dbc-sample/src/main/java/com/example/jooq/r2dbc/entities/Status.java (1)

6-6: New enum value PUBLISHED added.

jpa/multitenancy/schema/src/main/java/com/example/multitenancy/schema/utils/TenantNameType.java (1)

3-5: Introduced Lombok's @Getter for tenantName. This enhances code readability and maintainability by reducing boilerplate getter methods.

Also applies to: 12-12

jpa/multitenancy/multidatasource-multitenancy/src/main/java/com/example/multitenancy/utils/DatabaseType.java (1)

3-5: Utilized Lombok's @Getter for schemaName. This change promotes cleaner and more maintainable code by automatically generating getter methods.

Also applies to: 17-17

boot-opensearch-sample/src/main/java/com/example/opensearch/config/Initializer.java (1)

21-21: Ensure that properties.getCors() is always non-null before logging to prevent potential NullPointerExceptions.

Verification successful

properties.getCors() is always non-null before logging, as the getCors method in ApplicationProperties returns a non-null Cors object initialized with new Cors().

  • boot-opensearch-sample/src/main/java/com/example/opensearch/config/ApplicationProperties.java
  • boot-opensearch-sample/src/main/java/com/example/opensearch/config/Initializer.java
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify that properties.getCors() is always initialized before use.

# Test: Search for the initialization of properties in the codebase.
rg --type java $'properties ='

Length of output: 2442



Script:

#!/bin/bash
# Description: Verify that properties.getCors() is always non-null before logging to prevent potential NullPointerExceptions.

# Step 1: Search for the definition of `properties` in the Initializer class.
ast-grep --lang java --pattern 'class Initializer { $$$ $_ properties $$$ }'

# Step 2: Search for the initialization of `properties` in the Initializer class to ensure it is non-null.
rg --type java 'Initializer('

# Step 3: Check the implementation of the `getCors` method in the properties class to ensure it does not return null.
rg --type java 'public Cors getCors'

Length of output: 462



Script:

#!/bin/bash
# Description: Verify that properties.getCors() is always non-null before logging to prevent potential NullPointerExceptions.

# Step 1: Search for the definition of `properties` in the Initializer class.
ast-grep --lang java --pattern 'class Initializer { $$$ $_ properties $$$ }'

# Step 2: Correct the regex error and search for the initialization of `properties` in the Initializer class to ensure it is non-null.
rg --type java 'Initializer\('

# Step 3: Inspect the implementation of the `getCors` method in ApplicationProperties.java to ensure it does not return null.
rg --type java --context 5 'public Cors getCors' | grep -A 5 'ApplicationProperties'

Length of output: 4220

boot-opensearch-sample/src/test/java/com/example/opensearch/common/ContainersConfig.java (1)

12-12: The changes made to declare openSearchContainer as final and use method reference in dynamicPropertyRegistry.add are good practices for immutability and clarity.

Also applies to: 22-22

jpa/multitenancy/partition/src/main/java/com/example/multitenancy/partition/config/tenant/TenantIdentifierResolver.java (1)

13-13: The explicit specification of the generic type <String> enhances type safety and clarity.

jpa/multitenancy/schema/src/main/java/com/example/multitenancy/schema/config/multitenancy/TenantIdentifierResolver.java (1)

13-13: Consistent enhancement of type safety across different modules by specifying the generic type <String>.

r2dbc/boot-jooq-r2dbc-sample/src/main/java/com/example/jooq/r2dbc/config/JooqConfiguration.java (1)

26-26: Proper integration of ExceptionTranslatorExecuteListener to handle exceptions in JOOQ operations. Ensure this integrates well with the rest of the application error handling strategy.

Verification successful

The integration of ExceptionTranslatorExecuteListener in JooqConfiguration aligns with the existing global exception handling strategies in the application. This addition should enhance uniform exception handling for JOOQ operations without conflicts.

  • r2dbc/boot-jooq-r2dbc-sample/src/main/java/com/example/jooq/r2dbc/config/JooqConfiguration.java
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify integration of ExceptionTranslatorExecuteListener with application error handling.

# Test: Search for error handling configurations. Expect: Consistent configuration across the application.
rg --type java 'ExceptionTranslatorExecuteListener'

Length of output: 607



Script:

#!/bin/bash
# Description: Verify integration of ExceptionTranslatorExecuteListener with application error handling.

# Test: Search for general error handling configurations and strategies in the application.
rg --type java 'ExceptionHandler|ErrorHandler|@ControllerAdvice|@ExceptionHandler|ErrorController'

Length of output: 16042

jpa/multitenancy/multitenancy-db/src/main/java/com/example/multitenancy/db/config/multitenant/TenantIdentifierResolver.java (1)

13-13: Good use of Objects.requireNonNullElse to ensure robustness by handling potential null values effectively.

scheduler/boot-scheduler-quartz/src/main/java/com/scheduler/quartz/model/common/Message.java (1)

45-47: Consider making valid field immutable if not required, to ensure thread-safety.
[REFACTOR_SUGGESTion]

jpa/multitenancy/multidatasource-multitenancy/src/main/java/com/example/multitenancy/config/multitenant/TenantIdentifierResolver.java (1)

13-13: Good use of generic type parameter to enhance type safety.

graphql/boot-graphql-webmvc/src/main/java/com/example/graphql/services/PostDetailsService.java (1)

35-39: Ensure that the updated method handles Optional values correctly to avoid potential errors, such as NoSuchElementException.

public Optional<PostDetailsInfo> updatePostDetails(
    PostDetailsEntity postDetailsObj, PostDetailsRequest postDetailsRequest) {
    postDetailsObj.setDetailsKey(postDetailsRequest.detailsKey());
    PostDetailsEntity persistedDetails = postDetailsRepository.save(postDetailsObj);
    return findPostDetailsById(persistedDetails.getId());
}
jpa/boot-hibernate2ndlevelcache-sample/src/test/java/com/example/hibernatecache/TestApplication.java (1)

35-35: Good use of try-with-resources for managing file operations, ensuring that resources are properly closed.

httpClients/boot-web-client-mvc/src/main/java/com/example/rest/webclient/exception/GlobalExceptionHandler.java (1)

45-45: Making ApiValidationError non-static is a good change if instance-specific data from GlobalExceptionHandler is needed.

jpa/boot-hibernate2ndlevelcache-sample/src/main/java/com/example/hibernatecache/config/GlobalExceptionHandler.java (1)

36-36: Enhanced robustness by adding null checks with Objects.requireNonNull.

jpa/boot-jpa-locks/README.md (1)

17-18: The explanation of isolation and propagation levels is clear and informative.

graphql/boot-graphql-webmvc/src/main/java/com/example/graphql/services/AuthorService.java (1)

49-49: Ensure the use of Objects.requireNonNull aligns with the overall error handling strategy.

Verification successful

The use of Objects.requireNonNull in RestaurantService.java is part of a conditional check to ensure eventRaw is not null before accessing its getOperationType method. This aligns with the general strategy of preventing null pointer exceptions by validating inputs before usage.

Given that both instances in AuthorService.java and RestaurantService.java use Objects.requireNonNull to prevent null-related issues, it seems consistent with an overall error handling strategy aimed at avoiding null pointer exceptions.

  • AuthorService.java: Objects.requireNonNull(authorEntity)
  • RestaurantService.java: Objects.requireNonNull(eventRaw)

This demonstrates a consistent approach to error handling across service classes.

Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify consistent use of Objects.requireNonNull in other service classes.

# Test: Search for Objects.requireNonNull usage in other service classes. Expect: Consistent usage or error handling strategy.
rg --type java 'Objects.requireNonNull' --glob '*Service.java'

Length of output: 436



Script:

#!/bin/bash
# Description: Extract the context of Objects.requireNonNull usage in RestaurantService.java

# Extract 5 lines before and after the occurrence of Objects.requireNonNull in RestaurantService.java
rg --type java 'Objects.requireNonNull' --glob 'RestaurantService.java' -A 5 -B 5

Length of output: 1864

boot-strategy-plugin/docker-compose-app.yml (1)

8-8: Change port mapping syntax for clarity.

graphql/boot-graphql-querydsl/src/main/java/com/example/graphql/querydsl/entities/Post.java (1)

34-34: Ensure the mappedBy attribute is correctly set in the PostDetails relationship.

Verification successful

The PostDetails entity class has been located, and it contains a relationship with the Post entity. Here is the relevant section of the PostDetails class:

graphql/boot-graphql-querydsl/src/main/java/com/example/graphql/querydsl/entities/PostDetails.java:@Entity(name = "PostDetails")
graphql/boot-graphql-querydsl/src/main/java/com/example/graphql/querydsl/entities/PostDetails.java:public class PostDetails {
graphql/boot-graphql-querydsl/src/main/java/com/example/graphql/querydsl/entities/PostDetails.java:    private Post post;
graphql/boot-graphql-querydsl/src/main/java/com/example/graphql/querydsl/entities/PostDetails.java:    public PostDetails setPost(Post post) {

The PostDetails class has a field post that is mapped by the Post entity. To ensure the mappedBy attribute is correctly set, we need to verify that the Post entity's mappedBy attribute correctly references this field.

Given the previous context, the Post entity's annotation is:

@OneToOne(cascade = CascadeType.ALL, mappedBy = "post", orphanRemoval = true)

This indicates that the mappedBy attribute is correctly set to reference the post field in the PostDetails entity.

  • PostDetails class: private Post post;
  • Post class: @OneToOne(cascade = CascadeType.ALL, mappedBy = "post", orphanRemoval = true)

The mappedBy attribute is correctly set in the Post entity's relationship with PostDetails.

Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the consistency of the 'mappedBy' attribute in other entity relationships.

# Test: Search for 'mappedBy' usage in other entity classes. Expect: Consistent usage or correct mapping.
rg --type java 'mappedBy' --glob '*Entity.java'

Length of output: 750



Script:

#!/bin/bash
# Description: Locate PostDetails entity class and inspect its relationship with Post.

# Locate the PostDetails class
fd -e java 'PostDetails'

# Search for the relationship with Post in PostDetails class
rg --type java 'Post' $(fd -e java 'PostDetails')

Length of output: 18236

jpa/multitenancy/multidatasource-multitenancy/src/main/java/com/example/multitenancy/config/multidatasource/PrimaryDataSourceConfiguration.java (1)

40-42: Ensure the use of generics improves type safety without affecting existing functionality.

Verification successful

The use of generics in PrimaryDataSourceConfiguration and SecondaryDataSourceConfiguration is consistent and should not affect existing functionality while improving type safety.

  • PrimaryDataSourceConfiguration.java
  • SecondaryDataSourceConfiguration.java
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the impact of adding generics on related classes.

# Test: Search for related configurations in other datasource configurations. Expect: Consistent use of generics or proper handling.
rg --type java '<String>' --glob '*DataSourceConfiguration.java'

Length of output: 1014

jpa/multitenancy/multidatasource-multitenancy/src/main/java/com/example/multitenancy/config/multidatasource/SecondaryDataSourceConfiguration.java (2)

40-40: Adding the <String> generic type to MultiTenantConnectionProvider enhances type safety and clarity. Good change!


42-42: Specifying the <String> generic type for CurrentTenantIdentifierResolver is a prudent enhancement for type safety. Well done!

graphql/boot-graphql-webmvc/src/test/java/com/example/graphql/web/controllers/PostDetailsEntityControllerTest.java (1)

90-90: The update to wrap the return type with Optional in the test aligns with the changes in the method signature of updatePostDetails. This ensures that the test remains valid. Good update.

graphql/boot-graphql-webmvc/src/main/java/com/example/graphql/config/graphql/LocalDateTimeScalar.java (1)

58-67: Refactoring the parseValue method to use a switch statement with pattern matching greatly enhances the readability and maintainability of the code. This change effectively handles different input types in a cleaner and more structured way.

boot-opensearch-sample/src/main/java/com/example/opensearch/services/RestaurantSearchService.java (1)

129-129: The use of the final modifier on aggregationFunction ensures that the variable cannot be reassigned, promoting immutability and thread safety in your service class. This is a good practice, especially in a multi-threaded environment where the function could potentially be accessed by multiple threads.

jpa/boot-data-customsequence/src/test/java/com/example/custom/sequence/web/controllers/OrderControllerTest.java (1)

80-90: The method getOrderResponsePagedResult is now annotated with @NotNull, which ensures that null values are not returned and helps prevent potential NullPointerExceptions in your test methods. This is a good defensive programming practice. However, ensure that the method's implementation always adheres to this contract by not returning null values.

boot-mongodb-elasticsearch/src/test/java/com/example/mongoes/elasticsearch/repository/RestaurantESRepositoryIntegrationTest.java (9)

163-164: Refactoring to use getFirst() method simplifies and clarifies the retrieval of the first restaurant from search results.


212-213: Using getFirst() enhances consistency and readability when accessing the first restaurant from the search results.


240-241: Consistent use of getFirst() across different test methods helps maintain uniformity and improves code readability.


270-271: Continued use of getFirst() for accessing search results maintains clarity and consistency in the test code.


311-312: Applying getFirst() in additional test methods aligns with the overall refactoring strategy to improve clarity and code quality.


339-340: Systematic application of getFirst() across test methods demonstrates a strong commitment to code clarity and uniformity.


367-368: The pattern of using getFirst() is effectively applied here, enhancing readability and maintainability of the test suite.


393-394: The consistent use of getFirst() across various test methods standardizes the way search results are accessed, improving the test code structure.


449-450: The final instance of using getFirst() underscores the systematic approach to improving code readability and maintainability throughout the test class.

@@ -6,8 +6,7 @@ deleteDatasources:
- name: Prometheus
orgId: 1

# list of datasources to insert/update depending
# whats available in the database
# list of datasources to insert/update depending on what's available in the database
Copy link
Contributor

Choose a reason for hiding this comment

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

Please adjust the line length to adhere to best practices.

# list of datasources to insert/update depending on what's available in the database
Tools
yamllint

[error] 9-9: line too long (84 > 80 characters) (line-length)

@@ -6,8 +6,7 @@
- name: Prometheus
orgId: 1

# list of datasources to insert/update depending
# whats available in the database
# list of datasources to insert/update depending on what's available in the database
datasources:
# <string, required> name of the datasource. Required
- name: Prometheus
Copy link
Contributor

Choose a reason for hiding this comment

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

Correct the indentation level for the datasource configuration.

  - name: Prometheus
Tools
yamllint

[error] 12-12: wrong indentation: expected 2 but found 0 (indentation)

Comment on lines +48 to +50
@Setter
String msg;

Copy link
Contributor

Choose a reason for hiding this comment

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

Consider making msg field immutable if not required, to ensure thread-safety.

@@ -6,8 +6,7 @@ deleteDatasources:
- name: Prometheus
orgId: 1

# list of datasources to insert/update depending
# whats available in the database
# list of datasources to insert/update depending on what's available in the database
Copy link
Contributor

Choose a reason for hiding this comment

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

Consider breaking this line to adhere to the 80-character limit for better readability.

Tools
yamllint

[error] 9-9: line too long (84 > 80 characters) (line-length)

@@ -6,8 +6,7 @@
- name: Prometheus
orgId: 1

# list of datasources to insert/update depending
# whats available in the database
# list of datasources to insert/update depending on what's available in the database
datasources:
# <string, required> name of the datasource. Required
- name: Prometheus
Copy link
Contributor

Choose a reason for hiding this comment

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

Correct the indentation to match the YAML structure, expected 2 but found 0.

Tools
yamllint

[error] 12-12: wrong indentation: expected 2 but found 0 (indentation)

@@ -5,8 +5,7 @@ deleteDatasources:
- name: Prometheus
orgId: 1

# list of datasources to insert/update depending
# whats available in the database
# list of datasources to insert/update depending on what's available in the database
Copy link
Contributor

Choose a reason for hiding this comment

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

Consider breaking the line to adhere to the best practice of keeping line length under 80 characters. This enhances readability and maintainability.

-    url: http://host.docker.internal:9090
+    url: http://
+         host.docker.internal:9090

Committable suggestion was skipped due to low confidence.

Tools
yamllint

[error] 8-8: line too long (84 > 80 characters) (line-length)

httpClients/README.md Show resolved Hide resolved
@@ -4,8 +4,7 @@ apiVersion: 1
deleteDatasources:
- name: Prometheus

# list of datasources to insert/update depending
# whats available in the database
# list of datasources to insert/update depending on what's available in the database
Copy link
Contributor

Choose a reason for hiding this comment

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

Line exceeds recommended length. Consider breaking it into multiple lines for better readability.

-    url: http://host.docker.internal:9090
+    url: http://host.docker.internal:
+         9090

Committable suggestion was skipped due to low confidence.

Tools
yamllint

[error] 7-7: line too long (84 > 80 characters) (line-length)

@@ -5,7 +5,7 @@ services:
image: ghcr.io/rajadilipkolli/my-spring-boot-experiments/boot-strategy-plugin:latest
container_name: strategy-plugin-service
ports:
- 8080:8080
- "8080:8080"
Copy link
Contributor

Choose a reason for hiding this comment

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

Address trailing spaces to adhere to YAML best practices.

-            - "8080:8080" 
+            - "8080:8080"
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- "8080:8080"
- "8080:8080"

jpa/multitenancy/README.md Outdated Show resolved Hide resolved
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Outside diff range and nitpick comments (2)
jpa/multitenancy/README.md (1)

Line range hint 3-3: Correct the unordered list indentation for consistency.

- - MultiTenancy is a feature of JPA that allows you to store database data across multiple tenants. It's not a new concept—many applications have used it for years to separate data by tenant. However, Spring Data JPA provides an easy way to use multi-tenancy in your application by using Hibernate as your persistence provider.
+ - MultiTenancy is a feature of JPA that allows you to store database data across multiple tenants. It's not a new concept—many applications have used it for years to separate data by tenant. However, Spring Data JPA provides an easy way to use multi-tenancy in your application by using Hibernate as your persistence provider.
Tools
Markdownlint

5-5: Expected: 0; Actual: 1 (MD007, ul-indent)
Unordered list indentation

httpClients/README.md (1)

Line range hint 4-4: Remove trailing spaces to maintain clean and professional documentation.

- The HTTP client is built on top of the Java URLConnection class and provides a higher level of abstraction for handling HTTP requests and responses. 
+ The HTTP client is built on top of the Java URLConnection class and provides a higher level of abstraction for handling HTTP requests and responses.
Tools
Markdownlint

10-10: Column: 65 (MD010, no-hard-tabs)
Hard tabs

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 44e4b02 and 84a59b4.

Files selected for processing (3)
  • graphql/boot-graphql-webmvc/src/main/java/com/example/graphql/web/controllers/PostDetailsController.java (1 hunks)
  • httpClients/README.md (1 hunks)
  • jpa/multitenancy/README.md (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • graphql/boot-graphql-webmvc/src/main/java/com/example/graphql/web/controllers/PostDetailsController.java
Additional context used
Markdownlint
jpa/multitenancy/README.md

3-3: Expected: 0; Actual: 1 (MD007, ul-indent)
Unordered list indentation


5-5: Expected: 0; Actual: 1 (MD007, ul-indent)
Unordered list indentation

httpClients/README.md

4-4: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


10-10: Column: 65 (MD010, no-hard-tabs)
Hard tabs

Additional comments not posted (1)
jpa/multitenancy/README.md (1)

5-5: Correct the unordered list indentation for consistency.

- - This allows you to create a single entity class that can be shared by multiple tenants, giving each tenant its own independent instance of the data.
+ - This allows you to create a single entity class that can be shared by multiple tenants, giving each tenant its own independent instance of the data.

Likely invalid or redundant comment.

Tools
Markdownlint

5-5: Expected: 0; Actual: 1 (MD007, ul-indent)
Unordered list indentation

| [web-client-mvc](./web-client-mvc) | The application, demonstrates the way spring boot application will connect with external system using spring 5's webclient in a servlet environment |
| [web-client-webflux](./web-client-webflux) | The application, demonstrates the way spring boot application will connect with external system using spring 5's webclient in a reactive environment |
| [http client](./boot-restclient) | The application, demonstrates the way spring boot application will connect with external system using spring 6's restclient in a reactive environment |
| Name | Description |
Copy link
Contributor

Choose a reason for hiding this comment

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

Replace hard tabs with spaces to adhere to Markdown best practices.

- | Name                                            | Description                                                                                                                                           |
+ | Name                                            | Description                                                                                                                                           |

Committable suggestion was skipped due to low confidence.

Tools
Markdownlint

10-10: Column: 65 (MD010, no-hard-tabs)
Hard tabs

Copy link

Quality Gate Passed Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
2.7% Duplication on New Code

See analysis details on SonarCloud

@rajadilipkolli rajadilipkolli merged commit d351ec5 into main Jun 14, 2024
32 of 33 checks passed
@rajadilipkolli rajadilipkolli deleted the polish branch June 14, 2024 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment