The delta schema is clearly buggy / inconsistent, because we have never really exercised anything but the updates mechanism in it. Going forward I think it would make sense to split the current delta.json to separate schemas for
delta proper (updates etc)
subscribe/unsubscribe
request/response with put (add others here when documented properly)
and create a superschema for "stream message".
Previously we have had subscribe/unsubscribe specified twice, in delta.json and under messages separately.
This PR is an attempt to make the messages schema consistent and in line with the rest of the documentation.
fabdrol
commented
5 years ago
The delta schema is clearly buggy / inconsistent, because we have never really exercised anything but the updates mechanism in it. Going forward I think it would make sense to split the current delta.json to separate schemas for
and create a superschema for "stream message".
Previously we have had subscribe/unsubscribe specified twice, in delta.json and under messages separately.
This PR is an attempt to make the messages schema consistent and in line with the rest of the documentation.
See also #523.