google-gemini / google-gemini/gemini-cli
refactor(a2a-server): implement V1 to V2 settings migration logic
- Dominant language
- TypeScript
- Stars
- 107k
- Forks
- 14.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 45
Description
### What happened?
The 2a-server settings interface needs to be fully compatible with the V2 nested settings structure (settings.schema.json).
See [settings.ts](https://github.com/google-gemini/gemini-cli/blob/main/packages/a2a-server/src/config/settings.ts#L25-L27).
### What did you expect to happen?
This involves updating the Settings interface and implementing robust migration logic to support legacy V1 (flat) settings seamlessly. This should mirror the approach already implemented successfully in packages/cli/src/config/settings.ts.
### Client information
N/A - Feature Parity / Tech Debt
Contributor guide
Research direction
Start with packages/a2a-server/src/config/settings.ts and compare its Settings interface with the nested structure in settings.schema.json. Then read the migration approach in packages/cli/src/config/settings.ts. Done means A2A-server settings support V2 nesting while transparently migrating legacy flat V1 settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100