formField fails if custom unmarshaller is in scope
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.4k
- Forks
- 584
- Avg merge
- 14h 33m
- Merged PRs (30d)
- 24
Description
formField directive fails if there is too generic unmarshaller in scope, that prevents FieldMagnet machinery to work.
It can happen quite a lot - for example when using akka-http-json4s or other generic unmarshaller.
Reproducer https://github.com/marekzebrowski/akka-http-form-field-bug
If it is not solvable, maybe a word of warning in documentation, or a guide how to write own unmarshaller would be helpful
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
The payload names no repository files or tests; start with the linked reproducer and trace the formField directive and FieldMagnet machinery while a generic unmarshaller is in scope. Done means formField works in that situation, or the limitation is documented with guidance for writing an unmarshaller.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100