softwaremill / softwaremill/tapir
Consider translation of path variables and query params into fields in RPC messages
Open
Nobody has claimed this yet.
grpc
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 468
- Avg merge
- 5h 37m
- Merged PRs (30d)
- 34
Description
We may want to make a switch between HTTP and grpc fairly unnoticeable. Adding a way to translate an HTTP path (with path variables and query params) into an RPC message would be handy in this case.
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
No files, tests, or entry points are identified. Start by reviewing how Tapir maps HTTP endpoints to RPC messages and clarify which path variables and query parameters must become message fields. Done requires agreed translation rules and a defined implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100