-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
06.using-cards differences in card menu output (buttons in dotnet, list in nodejs) #1732
Labels
bug
Indicates an unexpected problem or an unintended behavior.
Comments
CoHealer
added
the
bug
Indicates an unexpected problem or an unintended behavior.
label
Aug 27, 2019
@emgrol I'm unable to repro this. I get the same buttons on both Node and C#. Node C#
|
I didn't make any changes to the samples and I had the latest samples, but it works fine now after updating the Emulator. Thanks for the suggestion, going to close this now that it was just an issue on my end. |
This was referenced Jul 18, 2020
This was referenced Sep 22, 2022
This was referenced Sep 22, 2022
This was referenced Sep 22, 2022
This was referenced Sep 22, 2022
This was referenced Sep 22, 2022
This was referenced Jan 10, 2023
This was referenced Jan 10, 2023
This was referenced Jan 10, 2023
This was referenced Jan 10, 2023
This was referenced Jan 10, 2023
This was referenced Jan 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sample information
Describe the bug
The dotnet bot displays buttons for the various card options while the nodejs bot shows a list of card options in a single text box.
To Reproduce
Run bots according to CLI instructions in respective READMEs
Expected behavior
Both bot should display card options menu as buttons, not a list.
Screenshots
dotnet bot: looks good, menu displayed buttons as expected
nodejs bot: bot displays list instead of buttons
Additional context
This may not be an issue with the sample itself and more so with the string formatting in ChoiceFactory.cs/js. @JonathanFingold ran me through the SDK and we came upon this after not seeing an immediately obvious points in the code samples that caused the formatting differences.
The text was updated successfully, but these errors were encountered: