You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The screenshot shows JSON captured through network trace.
Left one is Adaptive Cards sent through Streaming Extensions, same as raw JSON
Right one is Adaptive Cards sent through Direct Line channel, altered
Left one is through SE, with the Input.ChoiceSet in "compact" mode
Right one is through Web Socket, with the Input.ChoiceSet in "expanded" mode
Looks like in SE, if style is not set, it default to compact. But in Web Socket, if it is unset, it default to expanded (set explicitly through Direct Line channel).
This time, select "MockBot with Streaming Extensions"
Click "Open Web Chat in new window"
Type "card inputs"
Expected result
They are the same. Either both in expanded state or compact state.
I am unsure if we should change the current behavior. But sending the JSON as raw as possible sounds like a better idea to me. But on the other hand, we should not change users' expectations.
Background
We send Adaptive Cards from a bot, but the result is different if the AC JSON is sent through Streaming Extensions vs. Web Socket.
The original JSON sent from the bot can be found at https://github.com/compulim/BotFramework-MockBot/blob/master/src/commands/Cards/Inputs.ts.
The screenshot shows JSON captured through network trace.
Input.ChoiceSet
in "compact" modeInput.ChoiceSet
in "expanded" modeLooks like in SE, if
style
is not set, it default tocompact
. But in Web Socket, if it is unset, it default toexpanded
(set explicitly through Direct Line channel).Reproduce
Expected result
They are the same. Either both in expanded state or compact state.
I am unsure if we should change the current behavior. But sending the JSON as raw as possible sounds like a better idea to me. But on the other hand, we should not change users' expectations.
Additional context
It is probably related to this, #87 (comment).
The text was updated successfully, but these errors were encountered: