Cover `AdditionalExpectedResponses` as success responses
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Current TD specification introduced the concept of additionalResponses to model APIs that might return different payloads from the same affordance. This issue focuses on AdditionalExpectedResponses marked with the field success: true. In particular, the goal is to review the current status of the specification and understand the implications of supporting this Thing Description feature.
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 reviewing the linked Thing Description specification section for AdditionalExpectedResponses and the issue's stated goal. Determine the required behavior for responses marked success: true and document a clear implementation scope and completion criteria for the Scripting API.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100