-
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] Import changes from master #3458
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Get client properties from ServiceClient instead of OperationArguments
Add responseToBody method
Simplify OperationArguments
* Call progress callbacks in nodejs streams * Use tough-cookie instead of isomorphic-tough-cookie * Support progress reporting for non-stream scenarios * Add separate blob/stream and buffer/string progress tests
* Update mapper type definitions * Fix tests * Fix CompositeType className and modelProperties * Bump to v0.17.0
When constructing my sample I found this flag prevented webpack from including a redundant copy of the runtime in the bundle.
* RequestPolicyCreator -> RequestPolicyFactory * Bump to v0.18 * Update changelog for 0.18
Add base HttpResponse
Various improvements to our script infrastructure
* Pull in subset of isomorphic-xm2js * Update package.json * Update webpack configs * Add XML declaration when stringifying
* Move check everything to separate job * Update name
* [JS] [Service Bus] package.json in the samples folder The samples in the `samples` folder fail to run because they require users to install `@azure/service-bus` while they are inside of the source code of `@azure/service-bus`. NPM does this distinction by finding the nearest `package.json`. A rather simple fix for this is to add a `package.json` inside of the `samples` folder. The package is named `@azure@/service-bus-samples` and is not published as part of this PR. The README was updated to reflect the changes. Closes #3063
* rename files, refactor testing to use templates * read parameter to maxParallel * dry up common template steps * define EnvVars in tests-common.yml * use a storage-specific testing template * move archetype-sdk-tests-storage.yml and dry up tests.yml env vars
Bumped version of axios to 0.19.0
* Remove test dependent projects check * Split CI and PR pipelines
* Fix CI configuration errors * Remove downloading artifacts * Add external NPM task
* Fix CI configuration errors * Remove downloading artifacts * Add external NPM task * Add build job to CI pipeline * Bump the version
* Generate @azure/arm-resources package * Update versions
* Generate @azure/cognitiveservices-computervision package * Bump the version * Bump the version
* Generate @azure/arm-cosmosdb package * Bump the version * Bump the version
* Generate @azure/arm-sqlvirtualmachine package * Bump the version
* Remove line ending check from tslint config * Update npm scripts to reflect standard names A little bit of field reorganization was also added thanks to VS Code. * Add rimraf and update tunnel to 0.0.6 Updating tunnel fixes an issue in core-http tests where a `defaultPort` property was missing. * Lock tunnel to 0.0.6 and update cosmos lib to use it * Add ci.yml to enable CI builds * Add README headings required by doc-warden * Add sdk/core/core-http to README content issues list * Get headless browser tests running again * Fix build:test script * Try increasing timeout for nonexistent host test * Update repo URLs in package.json * Use 'mainFields' instead of deprecated 'module' in rollup options * Rename msRest to coreHttp * Add semicolon to appease linter * Fix module name in Rollup config
Migrate ms-rest-js into repo as @azure/core-http
- Fix build breaks due to transitive dependency "resolve" being bumped to 1.11.1
* [JS] [KeyVault] @azure/keyvault-secrets @azure/keyvault-secrets as an independent package. With a better README, inspired by the event-hub and our template repo.
* [JS] [KeyVault] @azure/keyvault-keys Separate package for KeyVault’s Keys. Related to #3230 Readme inspired by the guidelines and by the work done on @azure/service-bus
Merged locally and pushed. Closing this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes in this PR affecting storage sdks
#3456 - Pin resolve to 1.11.0
#2607 - Rename files to follow yaml file naming conventions
#3350 - eslint enabled on storage packages