Inconsistent example format for the type element
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 3
- Avg merge
- 20h 14m
- Merged PRs (30d)
- 1
Description
Originally submitted by rolandh (Roland Hedberg) on 2023-08-16
In the ID Token example in 5.3 evidence type is given as :
"type": {
"value": "document"
},
In other examples of responses this format is used:
"type": "document"
I get the difference between a response and a request. In requests the first variant is used consistently.
I think the second variant should be used for all response examples.
Bitbucket status: open
Bitbucket origin: issue 2038
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
Find the ID Token example in section 5.3 and compare its type element with the other response examples mentioned in the issue. Update the response example to use the consistent scalar format, then review the surrounding examples to confirm request formats remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100