Closed Dragomir-Ivanov closed 5 years ago
I don't recall any breaking changes, except that updating read-only non-scalar fields with the same value will not bail out. Same as updating scalar fields.
The breaking change is the change of the schema.Prepare
interface and implementation. We must consider any change to the public API a breaking change, no matter if it's commonly used by applications or not.
E.g. we call Prepare directly several places, where we have code working directly against the resource
layer without going through rest
.
Ah, I see now. Didn't considered someone to use Prepare
outside rest. I will add it to README.
Ah, I see now. Didn't considered someone to use
Prepare
outside rest. I will add it to README.
It's OK to wait untilll we have discussed/agreed on the interface change though 😉 Let's wait for @rs feedback.
This also means there will be no breaking changes.
On it.
@smyrman I have resolved all conversations and rebased the PR.
Going ahead with the merge then.
Fields stored in non-scalar form by
Storer
will differ from incoming JSON scalar form. Input scalars need to be converted to non-scalar form before comparison, so decision to be made if the field has changed. Closes #232