-
Notifications
You must be signed in to change notification settings - Fork 620
Description
Is your feature request related to a problem? Please describe.
As a developer working with Spring Boot, it's not straightforward to integrate with sciphi/r2r out of the box. I'm often frustrated by the manual setup required to configure clients, manage dependencies, and write boilerplate code to interact with the R2R service. This increases development time and introduces potential for inconsistencies across different Spring-based applications.
Describe the solution you'd like
I’d like to propose a Spring Boot starter module that provides a plug-and-play client for interacting with r2r. This starter would auto-configure a client bean, handle connection setup, provide simple abstractions (e.g., service interfaces), and allow configuration through application properties. It would drastically simplify usage for Spring developers by aligning with the typical Spring Boot conventions.
Describe alternatives you've considered
-
Manually creating a client in each project using standard HTTP libraries or WebClient, but this is repetitive and error-prone.
-
Creating a small internal library, but it lacks the polish, flexibility, and ease of adoption a proper Spring Boot starter could provide.
-
Using OpenAPI or Swagger generation tools, but they still require additional configuration and do not provide the Spring Boot idioms like
auto-configuration and conditional beans.
Additional context
A Spring Boot starter would help broaden adoption of r2r in the Java/Spring community. It could live in a separate module within the repo (e.g., r2r-spring-boot-starter) or as a companion repo. The starter could include examples, tests, and documentation to make onboarding seamless.