-
Notifications
You must be signed in to change notification settings - Fork 467
Open
Description
Currently, when HalFormsOptions.Inline#getInline is empty, the JSON inline attribute is excluded from the representation. This is because of:
spring-hateoas/src/main/java/org/springframework/hateoas/mediatype/hal/forms/HalFormsOptions.java
Line 39 in d6265fb
| @JsonInclude(Include.NON_EMPTY) |
If we take a look at HAL-FORMS specification, we can read what follows:
If the inline attribute is missing or unparseable and the link (see link) attribute is missing or unparseable, then the options element SHOULD be ignored.
Therefore, IMO, from the spec POV, inline has 3 states:
- missing
- empty
- non empty
Spring HATEOAS current behavior reduces this to 2 states:
- missing
- non empty
I think Spring HATEOAS should fix this to correctly represent the 3 states of the specification.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels