Open av185218 opened 12 hours ago
- Once the redirection is done, the WaveCX modal remains opened covering the underneath screen. To close it,
session-ended
event have passed to thehandleEvent
ofuseWaveCx
hook. Is that a correct approach?
@av185218 I believe the session-ended
event should only be triggered during logout, since starting a session is triggered upon user authentication only.
Thank you @SG185511. In that case, a way should be identified how the inner modal of WaveCX provider can be closed from outside.
@av185218 Yes, @SG185511 is correct. the session-ended event should only be used for the user session truly ending.
We like this general approach of allowing the consuming application to inspect/intercept links and will have an update out to allow that shortly (in the next day or two). We're working out exactly how everything will work, but most likely we will include a callback passed to those inspection functions that can be called to dismiss/close the modal content.
Dear Authors, Contributors
By using Your package to consume dynamic content that is displayed to users, a new requirement raised to make buttons rendered within the WaveCX webview deep link compatible - in other words, if a WaveCX contains a button that could be redirected within the mobile application, then it should be redirected. If not, the handling remains as is.
Now, to implement such capability, I need your help/advise:
session-ended
event have passed to thehandleEvent
ofuseWaveCx
hook. Is that a correct approach?Demo of the feature can be found here:
https://github.com/user-attachments/assets/e4a55d5f-29d2-4cec-911d-1835a6d3b300
Suggested Diff (as I couldn't raise a PR):
Sincerely,