feat(notifications): add launch + activationType to ToastNotification…#87
Open
PoliteZappah wants to merge 1 commit into
Open
Conversation
…Params and ToastNotificationButton
The Overwolf runtime already supports embedding a `launch` URI and
`activationType` in the underlying toast XML (matching the Windows
toast schema), but the TypeScript types did not expose these fields.
`launch` (string URI) + `activationType` ('protocol'|'foreground'|'background')
are added as optional fields on both `ToastNotificationParams` and
`ToastNotificationButton`.
With `activationType: 'protocol'` and a URI matching the app's
registered scheme, the OS invokes the URI via
`overwolf.extensions.onAppLaunchTriggered` (origin: 'urlscheme') when
the user clicks the toast — including from the Windows notification
center (Action Center) and on a cold start, which the in-process
`onToastInteraction` event cannot reach.
Motivated by OW-6562 / CF-10763.
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
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.
…Params and ToastNotificationButton
The Overwolf runtime already supports embedding a
launchURI andactivationTypein the underlying toast XML (matching the Windows toast schema), but the TypeScript types did not expose these fields.launch(string URI) +activationType('protocol'|'foreground'|'background') are added as optional fields on bothToastNotificationParamsandToastNotificationButton.With
activationType: 'protocol'and a URI matching the app's registered scheme, the OS invokes the URI viaoverwolf.extensions.onAppLaunchTriggered(origin: 'urlscheme') when the user clicks the toast — including from the Windows notification center (Action Center) and on a cold start, which the in-processonToastInteractionevent cannot reach.Motivated by OW-6562 / CF-10763.