-
Notifications
You must be signed in to change notification settings - Fork 360
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
Feature Request: Add handling for HAL responses #103
Comments
Nice request🤩, so what do you expect to achieve, could you describe it more specifically, very appreciate that |
When OpenBlocks gets a response from an API and that response is one of What happens now is that OpenBlocks treats the body of the response as an escaped JSON String. That means that for every response I need to have a Transformer to convert it back to JSON. If you look at the following image you can see that there is an array of devices on the path Adding the ability for OpenBlocks to handle HAL responses would extend or match the current behavior when the response is |
Hi @swright-eti , Very good point 😄 , we'll add this support in next release. |
Hey @swright-eti , a hot fix image for this issue has been published, please update Openblocks and give us a try 😄 |
I have tested this and it works. Thank you. |
Our REST APIs respond with either
application/hal+json
orapplication/problem+json
. Would it be possible to add these response types as something that OpenBlocks understands? That way I dont have to have a transformer for all the responses.Here is a doc from Spring about this: https://docs.spring.io/spring-hateoas/docs/current/reference/html/
The text was updated successfully, but these errors were encountered: