Skip to content
This repository was archived by the owner on Aug 10, 2026. It is now read-only.

[EDX-146] Address some differences between the IDL and the feature spec - #1462

Merged
tbedford merged 15 commits into
mainfrom
EDX-146-address-some-IDL-differences-with-feature-spec
Jun 27, 2022
Merged

[EDX-146] Address some differences between the IDL and the feature spec#1462
tbedford merged 15 commits into
mainfrom
EDX-146-address-some-IDL-differences-with-feature-spec

Conversation

@lawrence-forooghian

@lawrence-forooghianlawrence-forooghian commented Jun 15, 2022

Copy link
Copy Markdown
Contributor

Description

This addresses some differences between the IDL and the feature spec - sometimes by changing the IDL, sometimes by changing the feature spec. Please review commit-by-commit – the commit messages contain plenty of details.

@kennethkalmer
kennethkalmer temporarily deployed to ably-docs-edx-146-addre-hwjdek June 15, 2022 12:33 Inactive
@lawrence-forooghianlawrence-forooghian changed the title Edx 146 address some idl differences with feature spec[EDX-146] address some idl differences with feature specJun 15, 2022
@lawrence-forooghianlawrence-forooghian changed the title [EDX-146] address some idl differences with feature spec[EDX-146] Address some differences between the IDL and the feature specJun 15, 2022
@lawrence-forooghian
lawrence-forooghian marked this pull request as ready for review June 15, 2022 12:51
lawrence-forooghian added a commit that referenced this pull request Jun 15, 2022
This excludes what's already been addressed in #1459, #1460, #1461, #1462.
Comment threadcontent/client-lib-development-guide/features.textile Outdated
Comment threadcontent/client-lib-development-guide/features.textile Outdated
@kennethkalmer
kennethkalmer temporarily deployed to ably-docs-edx-146-addre-hwjdek June 16, 2022 19:39 Inactive
@lawrence-forooghian
lawrence-forooghianforce-pushed the EDX-146-address-some-IDL-differences-with-feature-spec branch from 5908a92 to aaeeeb5CompareJune 16, 2022 19:40
@kennethkalmer
kennethkalmer temporarily deployed to ably-docs-edx-146-addre-hwjdek June 16, 2022 19:41 Inactive
Comment threadcontent/client-lib-development-guide/features.textile
@lawrence-forooghian
lawrence-forooghianforce-pushed the EDX-146-address-some-IDL-differences-with-feature-spec branch from aaeeeb5 to 14f7526CompareJune 19, 2022 18:29
@kennethkalmer
kennethkalmer temporarily deployed to ably-docs-edx-146-addre-hwjdek June 19, 2022 18:29 Inactive
It’s more consistent with the rest of the spec and also the IDL.
@lawrence-forooghian
lawrence-forooghianforce-pushed the EDX-146-address-some-IDL-differences-with-feature-spec branch from 14f7526 to 17b377eCompareJune 20, 2022 13:36
@kennethkalmer
kennethkalmer temporarily deployed to ably-docs-edx-146-addre-hwjdek June 20, 2022 13:36 Inactive
In RTE5, “no arguments” is being used to mean “not even a listener” -
i.e. it treats a listener as an argument, which I think makes sense and
is consistent with the way listeners are represented in the IDL. So make
the rest of the spec consistent with this.
The spec implies that objects that implement the EventEmitter interface
are responsible for emitting their own events - i.e. there’s no reason
why a user of the library would want to tell an object to emit an event.
It mentions “optionally a JSON-encodable object”. It’s not clear what
this means – either it means that you can pass a JSON-encodable object
_in addition to_ or _instead of_ the DeviceDetails argument.
Either way, I can’t find anything to back this up. The IDL just allows a
DeviceDetails object, as do a few of our SDKs that I checked:
- ably-java@7fc1939
- ably-ruby@f5eac15
- ably-cocoa@aed6c60
- ably-js@48a66d6
RSC1a describes a _single_ String constructor that’s responsible for
deciding if the passed value is a a key or token.
These variants that take a DeviceDetails argument are not mentioned in
RSH1b1 or RSB1b4, and from a quick look at a few client SDKs it doesn’t
appear to be implemented in our SDKs either.
I think it’s better for the IDL to be complete than to avoid a little
duplication.
It’s still part of the public API of the SDK. (Also, for consistency,
since our other deprecated properties are in the IDL.)
@lawrence-forooghian
lawrence-forooghianforce-pushed the EDX-146-address-some-IDL-differences-with-feature-spec branch from 17b377e to 3e542b6CompareJune 20, 2022 13:42
@kennethkalmer
kennethkalmer temporarily deployed to ably-docs-edx-146-addre-hwjdek June 20, 2022 13:42 Inactive
@tbedford
tbedford merged commit eeccc7e into mainJun 27, 2022
@tbedford
tbedford deleted the EDX-146-address-some-IDL-differences-with-feature-spec branch June 27, 2022 10:58
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@lawrence-forooghian@Peter-Maguire@QuintinWillison@maratal@kennethkalmer@tbedford