-
Notifications
You must be signed in to change notification settings - Fork 275
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
TableStorage might be broken #277
Comments
I'll look into this shortly. |
There is no table storage class. https://github.com/Microsoft/botbuilder-js/tree/master/libraries/botbuilder-azure/src See this commit that removed the table storage class |
Up @Stevenic :) What's the alternative? The tutorials have to be updated accordingly :/ |
@Stevenic @stevengum I understand this was a part of the PR to remove some explicit middleware, but I'm not sure why table storage was completely removed as a state storage option with no alternative, while the other storage options remain. Can we get this put back in, or are you phasing out Azure Table Storage support? |
@csiebler we decided from a design perspective to move to supporting blob storage, as we believe supporting blob storage gives you the same functionality as table storage |
@sgellock Any reason not to support both? Is it a resource constraint in terms of code maintenance? If it’s definitely gone, can we spin it out as a separate community OSS modules? |
@sgellock Thanks for the update! |
@szul, yes. the decision to reduce our surface area was a big contributor for the change. We'd totally be supportive of the community spinning it out and making it a separate module. |
Hey,
It seems like
TableStorage
might be broken. WhileMemoryStorage
andFileStorage
are working fine, when switching toTableStorage
the following errors are thrown on the CLI after the first message is being sent to the bot:Console Error:
botbuilder
versions:The issue can be reproduced via this code:
I might be doing something wrong here, but according to the documentation, the code should be working.
Thanks,
Clemens
The text was updated successfully, but these errors were encountered: