* [Samples] updating to read from COMMUNICATION_SAMPLES_CONNECTION_STRING and removing endpoint
* [Samples] fixing formating
* [Samples] revert to use COMMUNICATION_CONNECTION_STRING
* [test.yml] introduce the cloud config
* [TestResource] updating new test resources
* [testyml] remove the int setting
* Update sdk/communication/test-resources.json as per Bert suggestion
Co-authored-by: Bert Ong <823691+beltr0n@users.noreply.github.com>
* [test-resource] fixing the case sensitive and adding azure subscription id
* [test.yml] fixing the config as per PR feedback
* [test..yml] update the format to add new line
* [testresource] remove communication_endpoint
Co-authored-by: Bert Ong <823691+beltr0n@users.noreply.github.com>
* update to preview 6
* update swagger file & tests
* change properties format
* remove RestUpdateMessageOptions from exposed api
* update package version to 1.1.0-beta.1
* check env in runtime to support react native
* update signaling client dependency version
* update changelog
* use shim for navigator
* update signaling to beta 5
* Increment package version after release of azure-communication-sms
* Increment package version after release of azure-communication-identity
* Increment package version after release of azure-communication-chat
* bump common version
* increment package version for autorest
* fix sms changelog
* additional fix for changelog
* formatting
* bump version that was missed by automation
* bump version for phone numbers
Co-authored-by: Bert Ong <823691+beltr0n@users.noreply.github.com>
* Moving tests under public folder
* enabling minmax jobs
* disabling minmax test for now
* moving files referencing generated under /internal
* nit fix command
`@azure/core-auth` added the `NamedKeyCredential` and `AzureNamedKeyCredential` symbols in version 1.3.0. Currently only `@azure/core-amqp` and `@azure/event-hubs` references these directly and need to be using 1.3.0, but updating in all packages that depend on it to satisfy rush.
* Upgrading to opentelemetry 1.0.0 (rc.0)
Did a few things that made this MUCH easier.
Now that everyone is using the createSpan from @azure/core-tracing we
no longer need _every_ project to reference opentelemetry/api! That has
been removed as part of this PR.
Unfortunately, the leaky nature of JS means that packages still need to
worry about opentelemetry when they build their browser bundle for
testing. To make that simpler I've added a common function to dev-tool
that everyone can call in their rollup that will give them the correct
named exports. This is hooked up for everyone at this point, so the next
time something like this happens I should be able to control it
centrally.
Now for the API breaking changes that I had to fix:
- CanonicalCode is gone and is replaced with SpanStatusCode.
SpanStatusCode has a much smaller set of codes (literally: ERROR, OK
or UNSET) so that simplified most of the way we were handling setting
a span status on error.
- There is a new field (`tracingContext`) that contains `Context`. You
now pass a context, not a span, to indicate what your "parent" is.
You'll see this where I've removed `SpanOptions.parentSpan`. Mostly
it's a simple replacement.
* add samples
* fix typo
* change readme
* samples fixes in JS, and links in READMEs
* fix after rebase
* Fix samples to use endpoint, updateMessage, and fix a bug in response deserialization
* address comment
Co-authored-by: Dominik Messinger <domessin@microsoft.com>
Related to #13723
This PR removes the tsconfig.json file from the lint script for the communication packages. As described in #10361, we no longer need to lint this file as long as it is extending from the common one.
This resolves about 12 linter errors in each of the communication packages.
Turns out these were the only errors for communication-common package, so removed the `|| exit 0` part so that future linter errors in this package are caught when they break the build
I confirmed with the TypeScript team that patch releases should not introduce breaking changes. This PR uses tilde in TypeScript version we use so get the latest patch releases for v4.1.
* [package] update the version number
* [autorest] generate new autorest
* [autorest] phone number generated
* [autorest] phone number generated from autorest
* [autorest] Update package version manually
* Increment package version after release of azure-communication-common
* Increment package version after release of azure-communication-phone-numbers
* Increment package version after release of azure-communication-identity
* Increment package version after release of azure-communication-sms
* Increment package version after release of azure-communication-chat
* Increment package version number
Co-authored-by: Josh Lai <joshlai@microsoft.com>
* update changelogs for release
* address PR comments
* bump chat version to beta.6
* Revert "bump chat version to beta.6"
This reverts commit 438c3d3659.
* Luc/Rename updateThread to updateTopic (#13820)
* rename update options
* rename update options
* update tests
* use communication user identifier model instead of communication user
* use communication user identifier model instead of communication user
* update recordings
* use communication identifier instead of using the generated model
* use common methods to map the models
* use common methods to map the models
* generate repeatability-Request-Id if not populated
* remove useless test method
* use CommunicationIdentifierKind
- Making some changes to simplify the "duplicate" models that we're exporting to mirror the opentelemetry models (addresses feedback from @xirzec and @bterlson)
- Switch core-tracing back to the `-preview` version naming style. Changing it mid-stream like we did breaks internal tooling.
* [communication-common] Add options bag for getToken function, mark @hidden where applicable
* rename url to endpoint in CommunicationIdentityClient constructor
* Update live test templates to use matrix generation
* Update sdk live tests to use matrix generation, cloud config stages
* Fix live test matrix filter parity errors
* Remove matrix filters. Opt-in most tests to samples and min/max testing
* Fix post step template parameter in monitor live tests
* Filter dependency version for live tests that don't support it
* Only publish test results for browser and node tests
As part of prepping for the next release of OpenTelemetry we found some code patterns that were going to become a large maintenance burden for us, primarily around the parenting of spans. To make this easier I've removed as many duplicate implementation of createSpan and tried to centralize everything into core-tracing instead.
This won't completely remove changes needed for a newer version of OpenTelemetry but it'll eliminate one of the bigger bottlenecks.
* [EventGrid] Update core-auth reference
In b6040c5451 we took a dependency on
some new surface area in @azure/core-auth. That has now been released as
version 1.2.0, so we bump our minimum dependency to that version.
The other packages have been updated as well, to keep versions consistent.
* [EventGrid] Prepare for 3.0.0-beta.3 release
* migrate changes from feature/communication-chat-2020-11-01-preview3
* migrate changes from feature/communication-chat-2020-11-01-preview3: format code
* Add live tests for realtime notifications (#13273)
* Add live tests for notifications
* Update recordings
* update signaling package version (#13430)
* Revert "Add live tests for realtime notifications (#13273)" (#13487)
This reverts commit 11b8e52cd5.
* Add back tests (#13597)
Co-authored-by: knvsl <10719831+knvsl@users.noreply.github.com>
This PR removes our dependency on the unmaintained package "karma-remap-istanbul" and replaces it with a smaller karma plugin ("karma-sourcemap-loader") that allows karma-coverage to load source maps from the disk correctly.
I tested and confirmed that the generated coverage data has the correct source TS files.
* [Docs] Upgrade typedoc to v0.15.2 to match that used by docs team
* standardize the docs script for cosmos, kv-admin, comm-common, and storage-internal-avro
## What
Audit Track 2 libraries and address any linting errors in package.json
Fixed anything that seemed safe, and anything that seemed like a
potential breaking change was confirmed with the owners or reduced
to a warning.
## Why
Another step towards being able to run the linter in our builds.
fixes#10597
This newly added command `docs` can help increase the quality of our documentation comments. It enables us to have a tight feedback loop on what is being generated as a documentation of our packages. I am pinning `typedoc` to v0.15.0 for now because this is the version being used for generating docs at `docs.microsoft.com`. This version should be updated when that team updates theirs.
Fixes https://github.com/Azure/azure-sdk-for-js/issues/12928
* upgrade TS version and fix compilation issues
* upgrade the linting parser version and fix new linting issues
* fix cosmos sample
* address feedback
* fix linting issues in formrecognizer tests
* use unknown instead of any across our code
* address more issues
* cleanup package.json in core-http
* revert noisy linting changes caused by vanilla eslint rules not TS aware
* allow the poller to have results of type void
* fixing samples
* fix keyvault-certificates' sample
JoshuaLai
luc
armansabaa
thdinizm
Orlando Watson
CHILIU-MSFT
Azure SDK Bot
Dominik
KarishmaGhiya
Ramya Rao
chradek
Richard Park
Lakshman Sundaralingam
knvsl
Deyaaeldeen Almahallawi
ankitarorabit
Bert Ong
Jianping Chen
Ben Broderick Phillips
Matt Ellis
Will Temple
Jeff Fisher
minnieliu
Maor Leger
Josue(MSFT)
Will Temple