Details
-
Task
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Won't Do
-
None
-
-
CP: ready for planning
-
3
-
Core: Platform
Description
Problem:
When a new optional property is added to the JSON Schema that describes a server-side entity we assume backwards compatibility (minor version increment).
However, if the very same JSON Schema definition file is used by the client the deserialization will fail due to the fact that FOLIO schemas include additionalProperties: false setting.
There is a mismatch here that needs to be addressed, some potential approaches include:
- change versioning policy so that even optional properties are considered breaking changes
- keep separate versions of schemas between servers and clients with the client version being more relaxed
- override "additionalProperties: false" when any given schema is used in the client context
We need to decide on the approach and document it on dev.folio.org
TestRail: Results
Attachments
Issue Links
- relates to
-
FOLIO-1718 extending guidelines on versioning
-
- Blocked
-
-
FOLIO-1735 Unable to login due to unrecognised staffSlips property when deserialising a service point
-
- Closed
-
-
MODUSERBL-64 Add staffSlips array to servicepoint.json
-
- Closed
-
-
MODUSERBL-65 Cannot login when additional properties are provided for service points
-
- Closed
-
-
MODUSERBL-89 Unrecognized field "customFields" (class org.folio.rest.jaxrs.model.User)
-
- Closed
-