-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Promote v16.1 to stable #674
Merged
Merged
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
* Initial commit * Remove example from webpack * Add manifest support * Add all provider types
* Update to take advantage of customData in pages in 13.1
* Add ordering of home results * Remove MS365 requirements * Update changelog * Merge main to 13.1
This change adds a microflow provider to the example platform to show how a platform developer could take advantage of OpenFin's Microflow support from within their platform in a configuration based way.
* Renamed microflows to low code integrations
Even though we are not treating this exactly as a module it is similarly configured and may be module based in the future.
* Added an example that shows the view options for iframes We didn't have an example of loading content and using the api view options to disable the fin api. And how would you allow that content to (1) update the view title (2) if needed broadcast and listen to context.
* Improve the endpoints that use fetch * Update changelog * Update changelog * Address feedback * Update local storage endpoint to support new format with metadata * Update schemas and docs * Update version usage * Add docs * Uodated changelog * Update changelog
…500) * Added support for sandboxing the iframe with some sensible defaults * Added gif
…nabled (#501) * Added support for synching context group and frame when fin and fdc3 is enabled on the frame Also added two examples one with fin api injection and one without.
* Update contacts and make configurable * Fix version numbering * Update offline versions
…y to map from platform to fdc3 app. (#505) * Added ability to use the mappings from other samples and added ability to map from platform to fdc3 app. * Linting and type generation
* Add template fragment examples * Update dependencies * Update readme --------- Co-authored-by: Martyn Janes <[email protected]>
Co-authored-by: Martyn Janes <[email protected]>
* Extract window positioning strategy and add monitor awareness * Added option of specifying default updatable preferences Also added a function that checks the apps or the defaults to see if a preference can be set. Updated view, window and native handling to reflect change. * Added support for monitor awareness to interop and actions * Updated docs and added monitor awareness to more actions - Updated docs - Added fix to utils position as it needed to consider that not all monitors start with 0,0 when checking to see if a window already exists in a position. - Updated launchView action to not rely on browser launch view but use an app structure so that it can take advantage of the launch preference capability. - Updated favorite to use launchPreferences. Passing undefined for window positioning strategy to go with defaults but more improvements are coming in this area.
* Add advanced form example * WIP * Add custom indicator * Improve advanced form sample
* Remove the quote and emoji code and dependencies * Fix dialog options assignment
- Added additional FDC3 support so that [context metadata](https://fdc3.finos.org/docs/api/ref/Metadata#contextmetadata) is passed when context is broadcast, an intent is raised or fdc3.open is used. This can be used with fdc3.getInfo to see if the context you received was sent from your app. - Updated example call app so that it logs the new context metadata when an intent is raised or context received. Added context support to the call app. Updated the example participant history app so that it console logs the context metadata received.
* Perform home search async instead of debounced * Remove debouncing from integrations * Update shapes * Update changelog * Individual ingtegration examples use new searching method
Added UnsavedPagePromptStrategy support to the browserProvider. This takes advantage of the enhancement in Workspace 16.1 to decide whether or not the page should prompt the user if it has unsaved changes (in the platform override: handleSaveModalOnPageClose). The options are: - "default" - use the default platform behavior - "skip-untitled" - any page that hasn't been assigned a title shouldn't prompt the user to save unsaved changes. - "never" - you never want workspace to show a prompt. Unsaved changes will be lost if the user doesn't save before closing.
* Added better support for native apps * Updated common folder across repo and updated launch logic - Native applications now use an appId for the UUID (if the uuid is not provided) and instanceId (if provided) - Support for replacing two tokens if specified in native app (external or app asset) command line args: {OF-PLAT-UUID} will be replaced with the UUID of the platform that launched the native app (useful if you want to validate that it is an expected UUID you are allowed to connect to) and {OF-EXT-UUID} which will pass the UUID we launched your external application with. - Updated the Winform Interop Example to be an updated copy that can auto connect if passed command line arguments and now supports raising more intents (ViewContact, ViewInstrument, ViewNews) and well as listening to those intents. A logging view has also been added. - BREAKING CHANGE: manifest.fin.json was the only manifest without a security realm specified. This has been updated but may result in saved data being lost when developing locally. We recommend a security realm to isolate your platform from others and so decided to apply it here as well. - Fixed - when launching multiple instances of an inline app asset it is possible to try and re-download an app asset that has just been downloaded or exists. We now fetch the app asset info to see if the platform already has the app asset and if it is the required version. * Updated snap logic to check a single string to see if it had multiple arguments * Updated the way native apps are identified for better intent support Updated identity returned when launching a native app or app asset (either normally or through snap). The UUID is the app id if the app has been marked as instanceMode = "single" otherwise the uuid is appId/guid (guid being an instanceId). The name is the same as the UUID (as name is not specified in app asset/external process options). If your app supports having multiple instances and it registers intent handlers then we recommend passing the created UUID for your app instance using {OF-EXT-UUD} as part of the command line args so that the uuid can be used when you connect to the OpenFin runtime. When you then connect to the workspace platform interop broker (as the platform will be waiting on that connection to fire an intent against it) it will use the expected UUID as it's connection id.
Update documentation.
johnman
requested review from
ameetj85,
camc314,
adam-saland and
joeransegnola
January 22, 2024 17:30
adam-saland
approved these changes
Jan 22, 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.
No description provided.