playframework / playframework/play-ws
WSClientConfig support for akka-http backend
Open
Nobody has claimed this yet.
status:backlog
type:upstream
- Dominant language
- Scala
- Stars
- 224
- Forks
- 92
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 28
Description
Currently configuration for akka-http backend is read from the configuration files (default functionality of akka-http).
This ticket is for adding support for the WSClientConfig.
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 tracing how the akka-http backend currently reads configuration files and where WSClientConfig would enter the client setup. Done means WSClientConfig is supported for the akka-http backend rather than relying only on akka-http's default configuration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100