Consider making client notification a stream
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by locating the client.onServerNotification API and the client effect backend that owns it, then trace how ServerNotification values are delivered. Define how client.serverNotifications(): Stream[ServerNotification] should coexist with the current API and verify that progress and logging notifications are observable through the stream.
Written by the indexing model from the issue text.
Description
Instead or along side of the current API:
client.onServerNotification:
case ServerNotification.Progress(params) => println(s"progress: ${params.progress}")
case ServerNotification.LoggingMessage(params) => println(s"log: ${params.data}")
case _ => ()
I would like to have a method that returns Stream[ServerNotification] specific to client effect backend.
client.serverNotifications(): Stream[ServerNotification]
- Dominant language
- Scala
- Stars
- 102
- Forks
- 10
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 19
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from softwaremill/chimp
-
tier:2 SDK
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
softwaremill/chimp#145 ·
Maintainers usually reply within 1 day
-
2026-07-28 version support
Difficulty 5/5 Over a week Newbie friendliness 35/100
softwaremill/chimp#255 ·
Maintainers usually reply within 1 day
-
2026-07-28 version support
Difficulty 5/5 Over a week Newbie friendliness 42/100
softwaremill/chimp#254 ·
Maintainers usually reply within 1 day
-
2026-07-28 version support
Difficulty 5/5 Over a week Newbie friendliness 45/100
softwaremill/chimp#253 ·
Maintainers usually reply within 1 day
-
2026-07-28 version support
Difficulty 5/5 Over a week Newbie friendliness 42/100
softwaremill/chimp#252 ·
Maintainers usually reply within 1 day
All issues in softwaremill/chimp
Similar issues
-
area:aggregation bug priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
apache/datafusion-comet#6661 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
salesforce/evalon#16 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
chipsalliance/chisel#5504 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 Half a day Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Homebrew formula 2.1.26: 'cs completions bash' fails (exit 127) because bin/cs is not executableOpen
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day