feat!: safari extension client status

[JAHMCR]

Added a listener to handle when the client state changes to notify event subscribers accordingly.

[dwosk]

@JAHMCR did you see my comment on the ticket about adding the listener for isKeepAlive?

It should be a relatively minor change (i.e. don't think we need to export any new functions, etc.)

// Register in Safari context
document.addEventListener('isAppAlive', (event) => {
  console.info('Desktop app running', event.detail.running);
});

When the SDK gets an event, it should have logic to trigger the registered status listeners (i.e. listeners registered via registerStatusCallback) if the desktop app went from running -> not running or vice versa.

[JAHMCR]

@JAHMCR did you see my comment on the ticket about adding the listener for isKeepAlive?

It should be a relatively minor change (i.e. don't think we need to export any new functions, etc.)

// Register in Safari context
document.addEventListener('isAppAlive', (event) => {
  console.info('Desktop app running', event.detail.running);
});

When the SDK gets an event, it should have logic to trigger the registered status listeners (i.e. listeners registered via registerStatusCallback) if the desktop app went from running -> not running or vice versa.

Yeah thanks, I will update the PR very soon

[dwosk]

Thanks @JAHMCR. It seems to work fine for me. Had Chrome and Safari side by side and saw the callbacks were triggered the same when I started/stopped the app.

[dabrad26]

Maybe can change to !item for all the item === undefined stuff. Do we have a type for the any on events. Maybe better if we can define event

[dabrad26]

We can probably just do !event.detail. Then we don’t need to explicit checking undefined as I assume we don’t want continue if null or empty string or anything.

[JAHMCR]

Done!