Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement batch operations feature #989

Closed
deanna-lad opened this issue May 23, 2022 · 0 comments · Fixed by #1410
Closed

Implement batch operations feature #989

deanna-lad opened this issue May 23, 2022 · 0 comments · Fixed by #1410
Assignees
Labels
enhancement New feature or improved functionality.

Comments

@deanna-lad
Copy link

deanna-lad commented May 23, 2022

Implement batch operations feature as described in the specification:
https://github.com/ably/docs/blob/main/content/client-lib-development-guide/features.textile#batch-operations

For reference please see: https://ably.com/docs/rest/batch

The original PR for spec creation: ably/docs#1421

Acceptance criteria: feature has been implemented and unit test has been written.

┆Issue is synchronized with this Jira Story by Unito

@deanna-lad deanna-lad changed the title Implement batch operations Implement batch operations feature May 23, 2022
@QuintinWillison QuintinWillison added enhancement New feature or improved functionality. and removed spec-alignment labels Dec 5, 2022
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit 85f1a39. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit 85f1a39. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit 85f1a39. Resolves #989.

TODO docs

TODO update signatures after updating spec
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Resolves #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Resolves #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Resolves #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Resolves #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Resolves #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 25, 2023
As described by spec at commit c2155c5. Resolves #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit c2155c5. Resolves #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit c2155c5. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit c2155c5. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit c2155c5. Resolves #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit c2155c5. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit c2155c5. Resolves #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit 595fdce. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit 595fdce. Part of #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit 595fdce. Resolves #989.

TODO docs
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit 0437830. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Part of #989.
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit 0437830. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Part of #989.
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit 0437830. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Resolves #989.
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit 0437830. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Part of #989.
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit 0437830. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Part of #989.
lawrence-forooghian added a commit that referenced this issue Jul 26, 2023
As described by spec at commit 0437830. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Resolves #989.
lawrence-forooghian added a commit that referenced this issue Jul 27, 2023
As described by spec at commit 0437830. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Resolves #989.
lawrence-forooghian added a commit that referenced this issue Jul 31, 2023
As described by spec at commit 0437830. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Note that the tests which revoke tokens do so using a random clientId.
This is to prevent the revocations performed in one test from having an
effect on tokens issued in a subsequent test. (I observed this
happening, and Simon confirmed that it's possible for a token issued
very shortly after a revocation to be affected by that revocation.)

Resolves #989.
lawrence-forooghian added a commit that referenced this issue Aug 1, 2023
As described by spec at commit 0437830. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Part of #989.
lawrence-forooghian added a commit that referenced this issue Aug 1, 2023
As described by spec at commit 0437830. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Part of #989.
lawrence-forooghian added a commit that referenced this issue Aug 1, 2023
As described by spec at commit 0437830. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Note that the tests which revoke tokens do so using a random clientId.
This is to prevent the revocations performed in one test from having an
effect on tokens issued in a subsequent test. (I observed this
happening, and Simon confirmed that it's possible for a token issued
very shortly after a revocation to be affected by that revocation.)

Resolves #989.
lawrence-forooghian added a commit that referenced this issue Aug 1, 2023
As described by spec at commit 18ef967. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Part of #989.
lawrence-forooghian added a commit that referenced this issue Aug 1, 2023
As described by spec at commit 18ef967. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Part of #989.
lawrence-forooghian added a commit that referenced this issue Aug 1, 2023
As described by spec at commit 18ef967. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Note that the tests which revoke tokens do so using a random clientId.
This is to prevent the revocations performed in one test from having an
effect on tokens issued in a subsequent test. (I observed this
happening, and Simon confirmed that it's possible for a token issued
very shortly after a revocation to be affected by that revocation.)

Resolves #989.
lawrence-forooghian added a commit that referenced this issue Aug 1, 2023
As described by spec at commit 18ef967. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Note that the tests which revoke tokens do so using a random clientId.
This is to prevent the revocations performed in one test from having an
effect on tokens issued in a subsequent test. (I observed this
happening, and Simon confirmed that it's possible for a token issued
very shortly after a revocation to be affected by that revocation.)

Resolves #989.
lawrence-forooghian added a commit that referenced this issue Aug 2, 2023
As described by spec at commit 18ef967. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Part of #989.
lawrence-forooghian added a commit that referenced this issue Aug 2, 2023
As described by spec at commit 18ef967. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Part of #989.
lawrence-forooghian added a commit that referenced this issue Aug 2, 2023
As described by spec at commit 18ef967. Documentation based on
sdk-api-reference repo at commit 652ef2f.

Note that the tests which revoke tokens do so using a random clientId.
This is to prevent the revocations performed in one test from having an
effect on tokens issued in a subsequent test. (I observed this
happening, and Simon confirmed that it's possible for a token issued
very shortly after a revocation to be affected by that revocation.)

Resolves #989.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or improved functionality.
Development

Successfully merging a pull request may close this issue.

3 participants