-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Storage V10 SDK - Where is table support? #4573
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithub |
Hi @phawxby Please refer to this Azure/azure-storage-js#45 |
Thanks @XiaoningLiu. I'll leave this one open as it's in the active repository. I'm disappointed that the recommendation is to just use the legacy API. |
I'm seconding the request for the table storage async implementation. I'm a bit surprised it's not at the top of the list considering Azure Table is pretty popular. |
Also here #5655 |
Hello all, We are closing this issue in favor of #5655 which will be updated soon once we have the first preview released of the new SDK for Tables that aligns with the Azure SDK guidelines as we have used for Blobs, Files, and Queues so far. Please subscribe to #5655 for further updates and thanks for your patience with us. |
Hello everyone! We are happy to announce that we have released the first Beta of the new Azure Tables SDK. It conforms to our new guidelines on writing JS SDKs for Azure services which ensure it will remain idiomatic, consistent and diagnosable. You can install it with Please share your feedback on the new design at #11179 and/or report any problems you find in a new GitHub issue. Looking forward to hear from you! |
Describe the solution you'd like
Promises/async/await support for Table storage. It doesn't appear to be part of the V10 SDK.
Describe alternatives you've considered
Promisfying the existing V2 SDK but that's a nightmare for typings and just really clunky, it should be natively supported.
Additional context
Current V2 SDK is referred to as legacy, it's not really legacy is there's no alternative. If there is an alternative it's not documented or has changed its name
The text was updated successfully, but these errors were encountered: