TODO: -2. Fix accept: / not working and falling back to the default. -1. Add the request body to the models resolver
- Investigate executing resolve/set via a custom ajv keyword
- Explicit assignment of wildcard default set/resolve functions to specific fields. array of names or something
- Can we get addAction's initial type to have some sort of validation? maybe generics? see postCollectionResource's PostCollectionActions type for an example.
- Can we pull out roads dependency? It seems to only be for the Response (and some types)
- defaultRequestMediaType should be optional, and shouldn't throw an error (resource.resolve)
- Add resource support for if-modified-since, etag
- don't send a content-type header if there's no response body (particularly with 204 responses) I THINK. Check spec
- Lower level Resource unit tests
- Lower level Representation unit tests
- Better docs
- Better support for json schema, resolve and set keywords. Maybe we need our own json schema lib.
- Have the router aware of the hostname, and serve different routes per hostname