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
Changing the behavior either way would be a breaking change, we may just need to use try/catch in JS and python and inspect error code in C#
clearab
added
P2
Nice to have
P1
Painful if we don't fix, won't block releasing
and removed
R8
Release 8 - March 16th, 2020
P2
Nice to have
labels
Feb 3, 2020
clearab
changed the title
[Skills] BotFrameworkKHttpClient.postActivity should not error out on non-2xx status codes
[Skills] BotFrameworkKHttpClient.postActivity should not error out on non-2xx status codes (language parity)
Feb 6, 2020
stevengum
changed the title
[Skills] BotFrameworkKHttpClient.postActivity should not error out on non-2xx status codes (language parity)
[Skills] BotFrameworkHttpClient.postActivity should not error out on non-2xx status codes (language parity)
Feb 28, 2020
Versions
SDK: 4.7.0
Describe the bug
BotFrameworkHttpClient should not throw error inside of axios and instead return the response and status code to the caller of
BotFrameworkHttpClient.postActivity()
Expected behavior
All status codes should be returned be surfaced to the bot and
axios
should not throw the error.axios#41
@gabog, @johnataylor, @axelsrz:
We could also change the C# implementation to blow up instead of accepting statusCodes not between 200-299.
[bug]
The text was updated successfully, but these errors were encountered: