Centralize Stargate load-balancer algorithm alias parsing
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 417
Description
Problem
Stargate deserializes algorithm names through both LoadBalancerAlgorithm and the tagged RawLoadBalancerAlgorithmConfig. Serde aliases are duplicated between these independent boundaries and can drift, causing a spelling to work in short configuration but fail in a detailed configuration object.
Desired outcome
Use one normalization path for algorithm names before parsing either configuration shape. Preserve algorithm-specific field validation and unknown-field rejection. Until then, keep parity tests covering every supported spelling in short configs, detailed configs, and routing overrides.
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 locating LoadBalancerAlgorithm and the tagged RawLoadBalancerAlgorithmConfig deserialization paths, then inspect existing parity tests for short configs, detailed configs, and routing overrides. Centralize algorithm-name normalization before either path while preserving algorithm-specific field validation and unknown-field rejection; done means every supported spelling behaves consistently in all three contexts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100