You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an embedded does not contain a self-link, a warning is printed and the item is ignored. While the spec looks contradictory, the embedded should not be ignored
The HAL spec is clear on this point:
The reserved "_links" property is OPTIONAL.
The HAL-FORMS spec looks contradictory since it states:
[the link element] is a RECOMMENDED element
and then (while this looks to break HAL backward compatibility)
Every HAL-FORMS document SHOULD have at least one link element in the collection with a key value set to self
[…]
Clients MAY reject a HAL-FORMS document that does not contain a link element with the key value set to self.
It recommends to defaults self-link to the URI used for the request but this looks incompatible with current cache handling in ketting since URI is used as a cache key
Is there any hope to have this behavior fixed?
The text was updated successfully, but these errors were encountered:
When an embedded does not contain a self-link, a warning is printed and the item is ignored. While the spec looks contradictory, the embedded should not be ignored
The HAL spec is clear on this point:
The HAL-FORMS spec looks contradictory since it states:
and then (while this looks to break HAL backward compatibility)
It recommends to defaults self-link to the URI used for the request but this looks incompatible with current cache handling in ketting since URI is used as a cache key
Is there any hope to have this behavior fixed?
The text was updated successfully, but these errors were encountered: