Updated samples to fdc3 2.0 & enhanced broker and notification service #746
Conversation
This file contains 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
Updated samples to use fdc3 2.0 instead of 1.2 to support richer getInfo calls. Updated WPS docs to promote 2.0 instead of 1.2 in the examples. Updated WPS Interop Override: - FDC3 open now supports passing context to all views it opens in a snapshot and not just the first one. We also check to see if it registers before firing based on a specified timeout. We don't await this so as not to slow down the response to the raiser. - FDC3 Intent Firing when targettng a snapshot now waits to fire the intent until each view registers an intent handler or times out. We don't await this so as not to slow down the response to the raiser. InstanceIds are only returned for single instance views/windows (not snapshots). Example notification service launch-app action now supports passing the appId and instanceId (id still needs to be specified) in the target field of customData. context can also be passed now. This will use fdc3.open. If you specify an instanceId and a timeout error is thrown (if the instance is no longer running) then it falls back to launching a new instance of the app and passing it the context if specified. - Updated example-notification-service-app to show raising a notification that has a call to action that passes data back to itself (or a new instance if it is closed) though a context listener.
johnman
requested review from
raycashmore,
ameetj85,
camc314,
adam-saland and
joeransegnola
camc314
approved these changes
Sep 29, 2024
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.
Updated samples to use fdc3 2.0 instead of 1.2 to support richer getInfo calls. Updated WPS docs to promote 2.0 instead of 1.2 in the examples.
Updated WPS Interop Override:
FDC3 open now supports passing context to all views it opens in a snapshot and not just the first one. We also check to see if it registers before firing based on a specified timeout. We don't await this so as not to slow down the response to the raiser.
FDC3 Intent Firing when targettng a snapshot now waits to fire the intent until each view registers an intent handler or times out. We don't await this so as not to slow down the response to the raiser.
InstanceIds are only returned for single instance views/windows (not snapshots).
Example notification service launch-app action now supports passing the appId and instanceId (id still needs to be specified) in the target field of customData. context can also be passed now. This will use fdc3.open. If you specify an instanceId and a timeout error is thrown (if the instance is no longer running) then it falls back to launching a new instance of the app and passing it the context if specified.