The HATEOAS client for javascript
action()
function on State classes would only return the default
action (@reda-alaoui).inv-by
Link relationship type from the [Linked Cache
Invalidation draft][2]. This link lets a resource tell the client that
it's cache should expire when the linked resource's cache also expires.New major version!
title
header is now considered to be an 'entity' / 'content'-header.Prefer-Push
. Browsers are basically dropping HTTP/2
Push, and not enough work is done to make this very interesting.
(More info).Content-Location
header, Ketting will automatically place the response body in the state cache. This means you could for example do a POST
request to create a new resource, and have your server respond with the newly created entity body + a Content-Location
header for the new resource location, and Ketting will pre-populate the cache for that new resource, potentially saving a round-trip.State
objects (which are returned from .get()
) now have a synchronous .follow()
and .followAll()
.application/problem+json
title
property on Siren fields.Resource.refresh()
is used.label
and value
were parsed in reverse.OptionDataSource
.2021-02-20
, which adds the 'options'
property.Prefer-Push
. Browsers are basically dropping HTTP/2
Push, and not enough work is done to make this very interesting.
More background.url.resolve
in node.follow()
and followAll()
methods.type
, status
, detail
, instance
properties to Problem
class, for better support of [application/problem+json
][6]. (@sazzer).Content-Location
header, the
response will now immediately get stored in the cache.draft-dalal-deprecation-header
][7]. Ketting will now emit
warnings if a Deprecation
header is detected, and will also provide
information from the Sunset
header and include the uri of the deprecation
link relation.target
, step
,
min
, max
, type
, minLength
, maxLength
, placeholder
, cols
, rows
.textarea
form field type.{cache: 'no-cache'}
with .refresh()
, not .get()
.