Value discrepancy
Open
Nobody has claimed this yet.
Specs
- Dominant language
- TypeSpec
- Stars
- 1.1k
- Forks
- 340
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 12
Description
For example, Message Activity:
"A3080: Senders SHOULD NOT include value fields of primitive types (e.g. string, int). value fields SHOULD be complex types or omitted."
Yet the impl will handle simple or complex types.
Contributor guide
No contributing guide indexed for this repository
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 reading the A3080 guidance for Message Activity and locating the implementation that handles value fields. Compare the expected treatment of primitive and complex values, then clarify whether the implementation or the specification needs changing. Done means the behavior and its tests or documentation agree with the resolved requirement.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100