_type is higher priority than `Content-Type`
Open
Nobody has claimed this yet.
question
- Dominant language
- TypeScript
- Stars
- 15
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Resources put with a _type key that value as the overall content type (in terms of scope checking at least) rather than the value given in the PUTs content-type header.
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 tracing the PUT resource handling and the scope-checking logic for resources containing a _type key. Compare the _type value with the PUT Content-Type header, then verify that scope checks use the intended value and add or update coverage for this behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100