Change Scheme Parameter
Open
- Dominant language
- Go
- Stars
- 6
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
The way the scheme is sent, it only uses the first one. We should make it make more sense.
_Originally posted by @troy0820 in https://github.com/Azure/operatortrace/pull/29#pullrequestreview-3039378182_
Contributor guide
Research direction
No file, test, or entry point is named. Start by locating the code that sends the scheme parameter and reproduce the current behavior where only the first value is used. Done means the scheme parameter is handled in the intended, more sensible way, with tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100