-
Notifications
You must be signed in to change notification settings - Fork 470
Link building does not consider method parameters declared in interfaces #1189
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
Labels
Milestone
Comments
You have an interface with |
Makes sense given support for Spring Web itself in spring-projects/spring-framework#15682. |
gregturn
added a commit
that referenced
this issue
Feb 7, 2020
gregturn
added a commit
that referenced
this issue
Feb 7, 2020
When forming links, look at a controller class's interface definitions for possible Spring Web annotations. Related issues: spring-projects/spring-framework#15682
gregturn
added a commit
that referenced
this issue
Feb 7, 2020
When forming links, look at a controller class's interface definitions for possible Spring Web annotations. Related issues: spring-projects/spring-framework#15682
gregturn
added a commit
that referenced
this issue
Feb 7, 2020
When forming links, look at a controller class's interface definitions for possible Spring Web annotations. Related issues: spring-projects/spring-framework#15682
gregturn
added a commit
that referenced
this issue
Feb 7, 2020
When forming links, look at a controller class's interface definitions for possible Spring Web annotations. Related issues: spring-projects/spring-framework#15682
Expanded scope of this issue to Spring MVC. |
odrotbohm
pushed a commit
that referenced
this issue
Feb 11, 2020
When forming links, look at a controller class's interface definitions for possible Spring Web annotations. Related issues: spring-projects/spring-framework#15682 Original pull request: #1194.
odrotbohm
added a commit
that referenced
this issue
Feb 11, 2020
Switched to a less complicated implementation of the interface method parameter annotation lookup by using Spring's ClassUtils.getInterfaceMethodIfPossible(…). Simplified test cases to pure unit test on the link builder APIs. We don't need to fully execute a complete MVC/WebFlux request/response cycle to verify the link creation to pick up the parameter annotations from the interfaces. Original pull request: #1194.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I generate all my Spring WebFlux methods in an interface from my Open API specification YAML file. The controller implements the methods in this interface. I also use WebFluxLinkBuilder to build my HATEOAS links in my returned response. However, unless the implementation has the @RequestParam/@PathVariable annotations, the generated links do not get resolved with the actual values. Ideally I shouldn't need to repeat what's in the interface in my implementation.
The text was updated successfully, but these errors were encountered: