When updating the location spec we realized that the specification lists all properties as optional (e.g. not required) and also none of them as nullable. In the SQL it is is the inverse: some of these properties can be nullable, and all of them are returned.
We should align the spec to the implementation.
On call we were leaning towards starting by updating the specification to reflect reality (rather than updating reality to reflect the specification) because clients are working with the implementation rather than the specification and this would potentially be a breaking change.
When updating the
locationspec we realized that the specification lists all properties as optional (e.g. notrequired) and also none of them as nullable. In the SQL it is is the inverse: some of these properties can be nullable, and all of them are returned.We should align the spec to the implementation.
On call we were leaning towards starting by updating the specification to reflect reality (rather than updating reality to reflect the specification) because clients are working with the implementation rather than the specification and this would potentially be a breaking change.