Skip to content

feat: move Notifications networks config to backend [GE-23]#7840

Draft
baptiste-marchand wants to merge 3 commits intomainfrom
feat/move-notifications-network-config-to-backend
Draft

feat: move Notifications networks config to backend [GE-23]#7840
baptiste-marchand wants to merge 3 commits intomainfrom
feat/move-notifications-network-config-to-backend

Conversation

@baptiste-marchand
Copy link
Contributor

Explanation

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TYSM!!

Great that we can clean this up!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note - this whole file can be thrown away once we start the push notification cleanup ticket
(push notifications are all derived from the server now, so we do not need any client side implementation to generate push messages).

@baptiste-marchand baptiste-marchand changed the title [GE-23] feat: move Notifications networks config to backend feat: move Notifications networks config to backend [GE-23] Feb 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants