[TD] Consequence of `contentType` being optional
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
The TD taskforce is discussing making contentType optional.
It is not only about ExpectedResponse and AdditionalExpectedResponse.
There are discussions that contentType MAY become optional in general and there is no default value kicking in like we do now with application/json.
I think we should try to understand the consequences (if any) from the Scripting API point of view.
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 reading the linked TD taskforce discussion and the Scripting API context around contentType, including ExpectedResponse and AdditionalExpectedResponse. Determine whether making contentType optional without a default affects the API, and document the resulting consequences or specification changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100