From bc2e462acd758eb9bc226a9459037fd2738794f6 Mon Sep 17 00:00:00 2001 From: Justin Baur <19896123+justindbaur@users.noreply.github.com> Date: Wed, 10 Dec 2025 11:40:39 -0500 Subject: [PATCH] Update libs/common/src/platform/server-notifications/README.md Co-authored-by: Derek Nance --- libs/common/src/platform/server-notifications/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libs/common/src/platform/server-notifications/README.md b/libs/common/src/platform/server-notifications/README.md index f5a54cbdd9a..630ab7bf490 100644 --- a/libs/common/src/platform/server-notifications/README.md +++ b/libs/common/src/platform/server-notifications/README.md @@ -81,7 +81,7 @@ That should largely have the same behavior and would allow us to maintain one fe The foreground implementation is specially for browser foreground instances. At the moment this service acts as a stub to avoid accidentally doubling up SignalR connections. If we had the default -implementation in both the background service worker and in each foreground instance anyone then +implementation in both the background service worker and in each foreground instance then there would be a web socket connection made in each. With this special instance we avoid that by doing nothing at the moment. Once we begin to fully support the `notifications$` observable we can make a choice whether or not keep not supporting it in the browser foreground or we can decide to support