connect: add description field to individual routes on a service-router
Open
theme/connect
type/enhancement
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
This will help document why routes may be super complicated.
Contributor guide
Research direction
Start by locating the service-router implementation and its individual route representation. Read how routes are currently defined and exposed, then determine the expected behavior for storing and surfacing a description; done means each route can carry an explanation of its complexity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100