Conversation
f1ca8c0 to
2203f17
Compare
2203f17 to
b903f90
Compare
lawrence-forooghian
left a comment
There was a problem hiding this comment.
As well as the comments below, I also wanted to mention that we need to write documentation comments for these new APIs and open a PR into https://github.com/ably/sdk-api-reference. The process described by EdX DR 5.4 isn't quite clear about when this should happen, but I’d suggest that it would be best to do it alongside the spec PR (i.e. now), so that reviewers of the spec PR can also understand how the new functionality is meant to be used by users.
b903f90 to
e3eb6fb
Compare
e3eb6fb to
24e8317
Compare
SimonWoolf
left a comment
There was a problem hiding this comment.
Looks good, couple comments
24e8317 to
08c4a9c
Compare
08c4a9c to
b1c42d0
Compare
b1c42d0 to
b511642
Compare
b511642 to
cfa3e5d
Compare
cfa3e5d to
9ee13a4
Compare
9ee13a4 to
9762cc3
Compare
9762cc3 to
2b8410c
Compare
lawrence-forooghian
left a comment
There was a problem hiding this comment.
Looks good, one outstanding question about the messageId response property, but feel free to resolve and merge if you consider it a non-blocker.
2b8410c to
38536ae
Compare
These were never implemented in any SDK so is safe to remove without deprectation
Co-authored-by: Lawrence Forooghian <lawrence@forooghian.com>
38536ae to
9d38a1c
Compare
Co-authored-by: Lawrence Forooghian <lawrence@forooghian.com>
9d38a1c to
97186e7
Compare
Resolves #140
Doing this now so that we can publish this as spec v2.1 before working on spec v3
Adds new specs for batch REST methods, using the new batch response format via the
newBatchResponsequery param.For further information, see: