hal-forms
hal-forms copied to clipboard
backward-compatible extension for HAL to support dynamic forms at runtime.
Is it possible to define required headers which need to be send along with the request using HAL-Forms? Examples would be - Authorization where a Bearer Token needs to be...
While `type` can guide the client which type of input to render, this still leaves room on how to render the value. For example a `number` can have a different...
I'm missing some types and would like to get some feedback if they might be implemented in the spec. - bool: Simple boolean values. Either true or false. Together with...
## Template key specification The [specification of the `_templates` collection](https://rwcbook.github.io/hal-forms/#templates-element) is a bit odd. It lists all properties, including the `key` property, when in fact – I think – `key`...
Is there any way to have a template define a list to which I can add and remove rows? E.g. if the model looks something like this: ``` { foo:...
https://rwcbook.github.io/hal-forms/#_code_type_code "Possible settings for the type value adn teh expected contents to be returned inthe are:" Should be?: "Possible settings for the type value and the expected contents to be...
This ticket in Spring HATEOAS makes obvious that the spec is currently not entirely clear which URI is to be assumed the default target for all state transitions described using...
Hi, in my opinion a template should allow a list of content types instead of only one. Format maybe like the http accept header.
Is it possible to define properties which accept arbitrary key/value pairs? For example when the server accepts a Map as request body. Like properties: * or so... ``` POST /foo...