riverqueue / riverqueue/river

Accessing river.Workers from the river.Client (or maybe all river.Config)

Open
#1,167 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
5.7k
Forks
179
Avg merge
15h 43m
Merged PRs (30d)
13

Description

So I initialize river.Client in a different place where I then register workers. It looks like currently I have to both create river.Workers, pass it to river.Client as river.Config, and then I have now pass both client and workers around to be able to both submit jobs and register workers. It would be nice if I could obtain workers from client instance. Or maybe even simply, to be able to access passed config stored inside river.Client. Maybe river.Client could get Config method returning river.Config?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how river.Client is constructed from river.Config and how river.Workers is registered. Decide whether the supported result should expose Workers or the stored Config; done means callers can submit jobs and register workers through the client without passing both objects separately.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.