Support for Path Parameters (Kotless DSL)
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
Does the Kotless DSL currently support path parameters? I understand the documentation is a work in progress, so I tried using a few different common patterns e.g. `/users/:id`, `/users/{id}` just to check, and none of them seem to be routed to my endpoint.
If it's the case that it's not yet implemented, I'd be happy to give it a shot, especially if anyone could point me to the right place for it.
Thanks!
**Update**: After looking through the source code, it's pretty obvious this just hasn't been implemented yet. It seems like the two parts to implementing this are parsing and matching the route in the dispatcher, and then generating the right Terraform output, does that sound about right?
Also, would a PR be accepted if it only implemented this feature for the Kotless DSL?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Kotless DSL route dispatcher and the code that generates Terraform output, since the issue identifies parsing, route matching, and infrastructure generation as the affected areas. Check how existing routes are represented and tested, then define completion as path-parameter routes such as /users/:id or /users/{id} reaching the endpoint with corresponding Terraform output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, terraform
- Domain
- api, backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100