-
Notifications
You must be signed in to change notification settings - Fork 472
Add SIREN support #334
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
Comments
+1 |
That would be great |
+1 |
Just released spring-hateoas-ext 0.2.0-beta5 to Maven central, it has a SirenMessageConverter. Configuration sample: https://github.com/dschulten/hydra-java/blob/master/hydra-sample/service/src/main/java/de/escalon/hypermedia/sample/Config.java It is based on AffordanceBuilder, which can also be found at the spring-hateoas affordances feature branch. I will merge in the latest changes from spring-hateoas-ext into the feature branch during the next days. |
+1 |
+1 |
+1, I hope spring team really looks at this, its being overlooked for more than 2 years. |
You may wish to revisit this light of #833 |
What happened to the Siren support? Seems like all the other issues that blocked this are closed or fixed? |
As a project we slowed on implementing new media types and instead shifting to other aspects like affordances, renaming “resource” to “model” and WebFlux support. But by making it easy for others to plug-in their own media type, nothing is stopping someone else from coding and publishing a module that supports SIREN (or whatever). |
The following is probably of interest to some of you: https://github.com/ingogriebsch/spring-hateoas-siren |
I think we should curate a list of well-known extensions on the project website and in the documentation to make sure users easily find those implementations. |
Any plan to add support for Siren? or a fluent API in order to generate HATEOAS entities in such way?
it would be interesting to add an integration with siren4j - https://github.com/eserating/siren4j.
The text was updated successfully, but these errors were encountered: