-
Notifications
You must be signed in to change notification settings - Fork 51
[N/A] Hook up event propagation for all browserview-related events #976
base: develop
Are you sure you want to change the base?
[N/A] Hook up event propagation for all browserview-related events #976
Conversation
Git
Asars used for testingTest results
|
|
Git
Asars used for testingTest results
|
Git
Asars used for testingTest results
|
src/browser/of_events.ts
Outdated
| if (tokenizedRoute.length >= 2) { | ||
| const [channel, topic] = tokenizedRoute; | ||
| const uuid: string = (payload && payload.uuid) || tokenizedRoute[2] || '*'; | ||
| const name: string|false = (payload && payload.name); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly irrelevant nitpick: will eval to undefined if there's no payload or no name.
(!!payload && payload.name) will evaluate to false if there's no payload, but I think unidentified is probably actually what we want in this case anyhow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. Is there a case in which this could not work as expected?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so. I would remove the |false typing, since this will never eval to false. But code looks good as is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, right, good call, missed that. Changed.
dhamberlin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
pbaize
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we restrict views to targets in the same app do we still need the custom window logic?
Git
Asars used for testingTest results
|
fd30fbd
|
The custom window logic is still necessary for |
Git
Asars used for testingTest results
|
Git
Asars used for testingTest results
|
|
After talking with Pierre and Tommy, changed the eventing scheme to the following:
The tests have been updated to reflect these changes. |
Git
Asars used for testingTest results
|
Description of Change
This PR adds propagated events up to Application and System for BrowserView.
Tests:
https://testing-dashboard.openfin.co/#/app/sessions/api/completed/5da8b1ceee166d7a14d451bc
Corresponding js-adapter PR:
HadoukenIO/js-adapter#357
@aziz512 trying to add you as reviewer but it won't let me for some reason.
Checklist
npm testpassesRelease Notes
Notes: