loadsys / loadsys/CakePHP-Serializers
Investigate ways of Disabling Deserailizing the Request Body Even With The Correct Content-Type Header
Open
Nobody has claimed this yet.
enhancement
question
- Dominant language
- PHP
- Stars
- 6
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Issue brought up in this thread: https://github.com/loadsys/CakePHP-Serializers/issues/107#issuecomment-104472285
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 with the linked discussion in issue #107, since this issue provides no file, test, or entry point. Trace how the request body is deserialized when the Content-Type header is correct, and finish by identifying a concrete way to disable that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100