Displaying forms is about allowing users to easily values the API requires the client to send back in its request. This tutorials demonstrates one way to map these values to the user and the current values in the representation. This is currently an underdeveloped as aspect of hypermedia clients and the extend to which to generalise this is up for debate.
Some general guidelines
- This component requires prior knowledge of form types from the API (eg ’http://types/text’) (this could be a reference collection or standardised based)
- This component only maps simple types and is thus highly constrained
- Generalised components are best for early modelling around simple collections
- Selects in this example only work on inline values (by value) rather than other collections (by reference)
- It would be possible to make these fully-featured, including layout configurable