Allow DAs to customize timeoutsand apps to control logging#1497
Allow DAs to customize timeoutsand apps to control logging#1497robmoffat merged 31 commits intofdc3-for-web-implfrom
Conversation
|
@robmoffat I think this and the new tests are working well now. N.b. I needed to test from the fdc3-get-agent package (although the timeouts are in the fdc3-agent-proxy package) as the custom timeouts are set by the DA in WCP3Handshake responses (which are the province of |
|
I had to merge the debug logging PR into this one to figure out the tests (needed debug output from the proxy messages). After doing so I realized that every call to broadcast on the current user channel is preceeded by a call to get the current user channel... I think this should be refined for performance reasons and the current user channel tracked in the channel support - there is, after all, a message sent when the channel is changed... Interested in your thoughts on that @robmoffat. |
|
@robmoffat not sure why netlify is ignoring this PR... |
I can't figure it out! @TheJuanAndOnly99 any ideas? |
…elete a redundant step
|
Closing to re-open (in case that wakes netlify up) |
1 similar comment
|
Hey @kriswest @robmoffat If I'm not mistaken Netlify will only generate previews for PRs made against the production branch |
|
@TheJuanAndOnly99 This PR got a preview and was targetting the same (non-main) branch: #1495 ...hmm its possible I raised that against main, then changed it... perhaps thats it. |
|
/netlify |
|
Switching to main as the base doesn't seem to get going on a build unfortunately. We might be in close and re-open territory. @robmoffat I'll make the changes to the logging args which should deal with all your comments then open as a new PR? |
Describe your change
Resolves two requested additions to getAgent/fdc3-for-web:
Adds the ability to control debug logging output from getAgent() and the DesktopAgentProxy via new arguments to getAgent(). The new arguments are documented in the types and documentation pages.
Allows DesktopAgents to set two custom timeouts, one for most FDC3 for Web message exchanges and a second for message exchanges that involve application launches. Also extends the default timeout for application launch message exchanges to 100 seconds and introduces standardized error messages for
ApiTimeout.Related Issue
resolves #1487
resolves #1488
Contributor License Agreement
Review Checklist
DesktopAgent,Channel,PrivateChannel,Listener,Bridging)?JSDoc comments on interfaces and types should be matched to the main documentation in /docs
Conformance test definitions should cover all required aspects of an FDC3 Desktop Agent implementation, which are usually marked with a MUST keyword, and optional features (SHOULD or MAY) where the format of those features is defined
The Web Connection protocol and Desktop Agent Communication Protocol schemas must be able to support all necessary aspects of the Desktop Agent API, while Bridging must support those aspects necessary for Desktop Agents to communicate with each other
npm run build) run and the results checked in?Generated code will be found at
/src/api/BrowserTypes.tsand/or/src/bridging/BridgingTypes.ts