-
Notifications
You must be signed in to change notification settings - Fork 0
[CallbackEvents] Unit tests #65
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
base: feature/callback-events
Are you sure you want to change the base?
Conversation
| */ | ||
| function _sendCallbackRequest(event) { | ||
| try { | ||
| const url = event.parsedMessageData ?? event.value; |
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.
Why should we remove this?
I think that this is needed for inlineEvents. When an event is inline, it doesn't have the parsedMessageData, and the URL value is in the event.value.
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.
On src/dash/DashAdapter.js line 499 we changed the value of messageData (which then is used to get parsedMessageData) to fix a bug where message_data was undefined, because value was received instead. In order to prevent errors, the logic to define which value to use (message_data or value) was moved to the Dash Adapter, so that decision is made before reaching src/streaming/controllers/EventController.js line 547 in this case. At this current point parsedMessageData is either message_data or value, depending the workflow.
test/unit/test/streaming/streaming.controllers.EventController.js
Outdated
Show resolved
Hide resolved
Co-authored-by: Sebastian Piquerez <[email protected]>
Co-authored-by: Sebastian Piquerez <[email protected]>
Co-authored-by: Sebastian Piquerez <[email protected]>
No description provided.