Azure/azure-sdk-for-js @azure/storage-file-share_12.0.0

on GitHub

2019.12 12.0.0

• [Breaking] The default browser bundle has been removed from the npm package. Bundling your application with a bundler such as Webpack is the recommended approach to building a browser bundle. For details on how to do this, please refer to our bundling documentation.
• [Breaking] The expiryTime and startTime members of the AccountSASSignatureValues and FileSASSignatureValues types, as well as the expiry and start members of the accessPolicy field of the SignedIdentifier type, have all been renamed to expiresOn and startsOn respectively for consistency with @azure/storage-blob and @azure/storage-queue.
• [Breaking] forceCloseAllHandles will return CloseHandlesInfo type instead of number.
• [Breaking] forceCloseHandle will return closedHandlesCount property instead of numberOfHandlesClosed to be compatible with CloseHandlesInfo.
• Updated to use OpenTelemetry 0.2 via @azure/core-tracing
• Bug Fix - Convert empty prefixes ("") to undefined when passed as options to the listFiles or listShares methods to avoid sending an invalid request to the service. Fixes bug 5817.
• The ShareFileClient.downloadToBuffer() helper method has a new overload where it is not required to pass a Buffer. The attributes offset and count are optional, and it downloads the entire file if they are not provided.
• [Breaking] shareName on ShareClient has been renamed to name. PR 6135
• ShareFileClient and ShareDirectoryClient now have a name property that returns the file or directory name respectively. PR 6135
• [Breaking] In browsers, blobBody on FileDownloadResponse has been renamed to contentAsBlob in order to avoid naming confusion between browser Blob objects and Blobs from @azure/storage-blob. PR 6183
• [Breaking] Removed uploadBrowserData from ShareFileClient in favor of a unified method uploadData that accepts both browser Blob objects as well as Node.js Buffer objects.
• Added a warning to the documentation of downloadToBuffer that explains the limitations of Node.js Buffer sizes to around 2GB on 64-bit architectures and 1GB on 32-bit architectures.
• Documented the behavior of getProperties methods with respect to metadata keys and their casing inconsistency when compared to the metadata keys returned through corresponding "list" methods with the includeMetadata option.