Drop `river_client` + `river_client_queue`
Open
Nobody has claimed this yet.
needs db migration
- Dominant language
- Go
- Stars
- 5.7k
- Forks
- 179
- Avg merge
- 15h 43m
- Merged PRs (30d)
- 13
Description
These were never put to work, and unless we find a reason they should exist soon, we should drop them on the next migration, especially now that river_producer is a thing.
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Locate the migration definitions for river_client and river_client_queue, then inspect how river_producer is represented and used. Done means the unused tables are removed in the next migration without affecting the active producer path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100