3 ms·
The elephant in the room for me is that while HATEOAS is mentioned, the impression I get from posts from developers online is that people program against a pre-
by miseg 11y ago
The elephant in the room for me is that while HATEOAS is mentioned, the impression I get from posts from developers online is that people program against a pre-agreed API format.
That's different to REST's automated discoverability for REST API clients.
- spdionis 11y agoIn my experience for most REST APIs use cases HATEOAS is not needed or not that useful. Writing a REST API for your mobile application? What do you need HATEOAS for? Do you really think it can replace documentation? On the other hand all the rest of nice bonuses of REST APIs are very useful in such a use case.
- miseg 11y agoExactly, that's where most implementations seem to decide against REST. I agree with you. The other parts of REST (if you agree that REST can be picked apart and still referred to as RESTful), as surely valuable.
- JackuB 11y agoBuilding SPA using Siren, it can be really useful for disabling parts of UI - when you have complex rules on whether user can list/edit/create resource, you just check if such action is in response and use its options. Yes, you can do same with bool flags in response, but if you structure all your decision making like this (around Resources and actions) it's quite easy and natural to make all your components react to un/availability of resource/action, thus accomodating even more complex scenarios - user can list, edit (only some), but can't create new.