Subscription stop misses InteractionInput ?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
At the moment, the Subscription interface looks like this
It seems the stop() method seems to miss InteractionInput as used elsewhere?
Note: the EventAffordance has cancellation information to be used..
Note2: the problem might arise from the fact that Subscription is used for events and (un)observing properties. The unobserveproperty has no way to indicate cancellation information.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the Subscription.stop() definition with the InteractionInput usage and the EventAffordance cancellation information mentioned in the issue. Also inspect how Subscription supports events versus observing and unobserving properties, especially unobserveproperty. Done means the API specification has an agreed, consistent way to represent cancellation information in all affected operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100