feat: upgrade notification services controller to v4 api#9384
Draft
zelkibuilds wants to merge 8 commits into
Draft
feat: upgrade notification services controller to v4 api#9384zelkibuilds wants to merge 8 commits into
zelkibuilds wants to merge 8 commits into
Conversation
Contributor
Author
|
@metamaskbot publish-preview |
Contributor
|
Preview builds have been published. Learn how to use preview builds in other projects. Expand for full list of packages and versions. |
zelkibuilds
added
the
team-notifications
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explanation
@metamask/notification-services-controllercurrently targets Notification API v3, which uses fixednotification_typevalues ("on-chain"/"platform") to distinguish notification shapes. The backend has moved to v4, wherenotification_typeandnotification_subtypeare producer-set database fields (e.g."wallet_activity"+"eth_sent"for on-chain,"perps"+"position_liquidated"for platform). Without this change, the controller continues calling v3 endpoints and types responses using the old discriminator model./api/v4/notificationsand/api/v4/notifications/mark-as-readschema.tsfrom the latest Notification API OpenAPI spec (v4 + legacy v1–v3 schemas)NotificationOutputV4,PlatformNotificationV4,OnChainNotificationV4)isOnChainNotification()/isPlatformNotification()— on-chain is identified bynotification_type === "wallet_activity"toRawAPINotification()to normalize v4 responses into the existing internal model:typefrompayload.data.kind(preserves existing processor routing)typetoTRIGGER_TYPES.PLATFORMregardless of producernotification_type(e.g."perps"), soprocessNotification()routing continues to workReferences
https://consensyssoftware.atlassian.net/browse/GE-330
schema.tsregeneration)notification_type === "on-chain" | "platform"must migrate to v4 values and/or useisOnChainNotification()/isPlatformNotification()Checklist