real content-type negotiation for klein.Plating
Open
Nobody has claimed this yet.
feature
- Dominant language
- Python
- Stars
- 838
- Forks
- 123
- Avg merge
- 7h 58m
- Merged PRs (30d)
- 12
Description
Right now it's based on the ?json=1 query string, which is convenient, but also slightly wrong; it's a workaround for people to manually type into their URL bar. It should be based on the Accept: header.
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 locating klein.Plating's handling of the ?json=1 query string and inspect how incoming request headers are exposed. The change is complete when content negotiation uses the Accept: header rather than relying on the query-string workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100