Support copying body with custom encoder
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
No file or test is named in the issue. Start by tracing how plug_loopback copies or encodes conn.body_params, then determine where a caller-supplied encoder can be selected. Done means custom formats such as XML can be reconstructed from body_params when the caller provides the appropriate encoder.
Written by the indexing model from the issue text.
Description
We need to provide an option to specify with which encoder to encode the conn.body_params in case we have a custom format.
For instance the request body could be an XML doc. We need to convert it back to XML from body_params (or any other field) and only the user can help us by specifying the right encoder.
- Dominant language
- Elixir
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from tanguilp/plug_loopback
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in tanguilp/plug_loopback
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
carverauto/serviceradar#4596 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
agentjido/jido_harness#80 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
sevenseacat/cinder#235 ·