### Packages impacted by this PR
This PR includes the JavaScript/Typescript SDK for health deid service.
It includes:
- tests
- samples
- Readme
### Issues associated with this PR
### Describe the problem that is addressed by this PR
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
---------
Co-authored-by: Harsha Nalluru <sanallur@microsoft.com>
### Packages impacted by this PR
@azure/eventgrid-system-events
### Issues associated with this PR
NA
### Describe the problem that is addressed by this PR
1. Originally, there was one unified package -
[`@azure/eventgrid`](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/eventgrid/eventgrid).
This package was generated from Swagger specification.
2. Earlier in April 2024, some parts of the `@azure/eventgrid` package
were extracted out to create a new package -
[`@azure/eventgrid-namespaces`](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/eventgrid/eventgrid-namespaces).
This package was generated from Typespec specification.
3. Now, with this PR, we are looking at the second split of the
`@azure/eventgrid` package. All System Events have been extracted out of
the swagger specification to Typespec specification. This is a new
package named `@azure/eventgrid-system-events`.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
1. In the Typespec core generator, We have an issue where client name
overrides are not applied to `alias`. I have created an issue
https://github.com/microsoft/typespec/issues/3240 to fix this. In the
meantime, I have handled this issue in the custom code.
2. With the new generator, `Known*` models are not generated. I have
created an issue
https://github.com/Azure/autorest.typescript/issues/2476 to fix this. In
the meantime, I have handled this issue in the custom code.
3. In the previous generator, we had several properties which were
overridden as mandatory parameters. With the new generator, such mass
overrides are not possible. So, we are allowing them to be optional and
close to the Wore specification. This is in parity with the other
language SDKs.
### Are there test cases added in this PR? _(If not, why?)_
No. They are all model objects. No code functionality is involved.
### Provide a list of related PRs _(if any)_
1. https://github.com/microsoft/typespec/issues/3240
2. https://github.com/Azure/autorest.typescript/issues/2476
3. https://github.com/Azure/azure-sdk-for-js/pull/29245
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
`npx tsp compile client.tsp`
### Checklists
- [X] Added impacted package name to the issue description
- [X] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [X] Added a changelog (if necessary)
@xirzec @joheredi @lmazuel FYI......
---------
Co-authored-by: Harsha Nalluru <sanallur@microsoft.com>
### Packages impacted by this PR
@azure-rest/ai-vision-face
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Generate and implement Face SDK via TypeSpec.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
---------
Co-authored-by: SDKAuto <sdkautomation@microsoft.com>
Co-authored-by: Chung Sheng Fu <Chung.Fu@microsoft.com>
### Issues associated with this PR
[User Story
3635039](https://skype.visualstudio.com/SPOOL/_workitems/edit/3635039):
[Alpha3][NodeJS][Hold/Unhold][SDK] Add Hold/Unhold APIs.
### Describe the problem that is addressed by this PR
Adding the hold and unhold feature to sdk
---------
Co-authored-by: Vinothini Dharmaraj <v-vdharmaraj@microsoft.com>
### Packages impacted by this PR
@azure/notifications-hub
### Issues associated with this PR
Contributes to #28750 but completion requires updating all the packages
to use this
### Describe the problem that is addressed by this PR
Building off of @jeremymeng's work in #27646, this PR configures API
review files for packages containing subpath exports.
While APIView is not yet ready to support multiple json files, this
provides us with appropriate API reviews tracking any public API changes.
Follow-up PRs will add support for this in APIView, but this feels like
a quick win and step forward.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
A few alternatives, and I am open to feedback:
1. Update the EngSys script to allow multiple DocModel json files - I
chose to go with a flag to disable generating them instead, so that we
can build off of it in pieces
2. File naming convention - I already got and applied some feedback on
that, thanks Timo
### Packages impacted by this PR
@azure/monitor-query
### Issues associated with this PR
NA
### Describe the problem that is addressed by this PR
`@azure/monitor-query` is scheduled for a GA next week. A new
`MetricsClient` is introduced with this GA release.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
No special design considerations.
### Are there test cases added in this PR? _(If not, why?)_
Yes.
### Provide a list of related PRs _(if any)_
NA
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
NA
### Checklists
- [X] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [X] Added a changelog (if necessary)
@srnagar @KarishmaGhiya Please review and approve the PR
---------
Co-authored-by: Srikanta <51379715+srnagar@users.noreply.github.com>
### Packages impacted by this PR
@azure/core-client
### Issues associated with this PR
N/A, follow up on #28631
### Describe the problem that is addressed by this PR
If you are exporting both CommonJS and ESM forms of a package, then it
is possible for both versions to be loaded at
run-time. However, the CommonJS build is a different module from the ESM
build, and thus a different thing from the
point of view of the JavaScript interpreter in Node.js.
https://github.com/isaacs/tshy/blob/main/README.md#dual-package-hazards
tshy handles this by building programs into separate folders and treats
"dual module hazards" as a fact of life.
One of the hazards of dual-modules is shared module-global state.
In core-clientwe have a module-global operationRequestMap that is used
for deserializing. In order to ensure it works in this dual-package world we
must use one of multiple-recommended workarounds.
In this case, the tshy documentation provides a solution to this with a
well-documented path forward. This is what is implemented here.
Please refer to
https://github.com/isaacs/tshy/blob/main/README.md#module-local-state
for added context
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
The obvious alternative is to just not do anything since tests have not
been failing; however, that
seems risky. While _this_ particular issue has not come up in tests, a
similar one came up for core-tracing.
I am open to just _not_ doing anything of course - I love not adding
code so just give me a reason!
### Packages impacted by this PR
### Issues associated with this PR
### Describe the problem that is addressed by this PR
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
---------
Co-authored-by: Asaf Levi <asaflevi@microsoft.com>
Co-authored-by: KarolGel <138193722+KarolGel@users.noreply.github.com>
Co-authored-by: tomsft <138026577+tomsft@users.noreply.github.com>
Co-authored-by: Karolien Gellynck <kgellynck@microsoft.com>
Co-authored-by: Tom Deray <tomderay@microsoft.com>
### Packages impacted by this PR
### Issues associated with this PR
### Describe the problem that is addressed by this PR
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
---------
Co-authored-by: SDKAuto <sdkautomation@microsoft.com>
Co-authored-by: Mary Gao <yanmeigao1210@gmail.com>
### Packages impacted by this PR
- @azure/notification-hubs
### Issues associated with this PR
N/A
### Describe the problem that is addressed by this PR
Adds support for [Firebase Messaging
V1](https://firebase.google.com/docs/cloud-messaging) following the PR
from the Azure Notification Hubs Team
https://github.com/Azure/azure-notificationhubs-dotnet/pull/302
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
Yes
### Provide a list of related PRs _(if any)_
https://github.com/Azure/azure-notificationhubs-dotnet/pull/302
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)
### Packages impacted by this PR
@azure/eventgrid
### Issues associated with this PR
NA
### Describe the problem that is addressed by this PR
The EventGrid Service Team has added 14 new events. The SDK must be
regenerated to include the code changes related to these 14 new events.
The SDK minor version has been updated.
- `Microsoft.Storage.StorageTaskAssignmentQueued`
- `Microsoft.Storage.StorageTaskAssignmentCompleted`
- `Microsoft.AVS.ScriptExecutionStarted`
- `Microsoft.AVS.ScriptExecutionFinished`
- `Microsoft.AVS.ScriptExecutionCancelled`
- `Microsoft.AVS.ScriptExecutionFailed`
- `Microsoft.AVS.PrivateCloudUpdating`
- `Microsoft.AVS.PrivateCloudUpdated`
- `Microsoft.AVS.PrivateCloudFailed`
- `Microsoft.AVS.ClusterCreated`
- `Microsoft.AVS.ClusterDeleted`
- `Microsoft.AVS.ClusterUpdating`
- `Microsoft.AVS.ClusterUpdated`
- `Microsoft.AVS.ClusterFailed`
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
There are no specific/complex design scenarios for this task. It is a
straightforward regenerate and some standard changes to the custom layer
of the code.
### Are there test cases added in this PR? _(If not, why?)_
No. This item is standard and we need not add test cases for every new
events. The existing cases would be sufficient.
### Provide a list of related PRs _(if any)_
- https://github.com/Azure/azure-sdk-for-js/pull/27384 (This is the PR
that adds similar events to the SDK in the 4.15.0 release)
- https://github.com/Azure/azure-sdk-for-js/pull/26939 (This is the PR
that adds similar events to the SDK in the 4.14.0 release)
- https://github.com/Azure/azure-sdk-for-js/pull/26020 (This is the PR
that adds similar events to the SDK in the 4.13.0 release)
- https://github.com/Azure/azure-sdk-for-js/pull/28176 (This is the PR
that adds similar events to the SDK in the 5.1.0 release)
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
`autorest --typescript swagger\README.md`
### Checklists
- [X] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [X] Added a changelog (if necessary)
### Packages impacted by this PR
New package: @azure/openai-assistants
Generated from [initial typespec for Assistants
PR](https://github.com/Azure/azure-rest-api-specs-pr/pull/15866)
### Issues associated with this PR
### Describe the problem that is addressed by this PR
New package for OpenAI Assistants API
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
---------
Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com>
### Packages impacted by this PR
@azure/identity
### Issues associated with this PR
N/A
### Describe the problem that is addressed by this PR
As we start to cleanup and refactor Identity, one of the low hanging
fruits we can remove right now is the MsalBaseUtils class
which all the MsalFlows inherit from. By standardizing here we can start
to peel away some of the inheritance based indirection
and move towards composition of smaller building blocks.
I tried to minimize the number of changes and make this a pure refactor,
as 1:1 to the existing behavior as possible while we
work out the larger refactor of the Msal inheritance based flows.
### Packages impacted by this PR
### Issues associated with this PR
### Describe the problem that is addressed by this PR
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
### Packages impacted by this PR
### Issues associated with this PR
### Describe the problem that is addressed by this PR
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
This is an update that combines changes from released changes (1.0/1.1)
to latest feature Main branch. See below for all changes.
- Updated versions to 1.2 Beta
- Various updates to match released versions
- Swagger Regenerated with latest api
- GA2 changes applied
- Unit test updated
---------
Co-authored-by: Min Woo Lee 🧊 <77083090+minwoolee-ms@users.noreply.github.com>
### Issues associated with this PR
NA
### Describe the problem that is addressed by this PR
- Introducing Map Search V2 SDK generated by [the backend API
definition](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/maps/data-plane/Search/stable/2023-06-01/search.json).
- The V2 APIs is not backward compatible; this is approved by the API
review board. In SDK side, we decide to do backward compatibility by
giving instruction to the users as follow:
- Install two version separately as dependencies
```json
{
"dependencies": {
"@azure-rest/map-search-v1": "npm:@azure-rest/map-search@^1.0.0",
"@azure-rest/map-search-v2": "npm:@azure-rest/map-search@^2.0.0"
}
}
```
- Import them saperately:
```js
import MapSerachClientV1 from "@azure-rest/map-search-v1";
import MapSearchClientV2 from "@azure-rest/map-search-v2";
```
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
The other consideration is adding a new package for search V2. We will
migrate to V2 eventually and we will only apply bug fixes for V1, thus
we decided to bump the major version. Also, since `^1.0.0` is still in
public-preview, it's safe for SDK side to introduce breaking changes
without a version bump.
### Are there test cases added in this PR? _(If not, why?)_
NA
### Provide a list of related PRs _(if any)_
NA
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [x] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)
This PR
- [x] Code generated from Typespec
- [x] Changelog
- [x] Port all the Tests from FR
- [x] Push recordings to assets repo
- [x] Samples-dev, JS, and TS
- [x] Readme
- [x] Readme getting started samples
- [x] Sample.env
- [x] CI
- [x] Live test pipeline
- [x] test-resources.json
Future PR
- [ ] Browser tests
- [ ] AAD (service doesn't support yet for this preview)
- [ ] Add back API REF link
### Packages impacted by this PR
communication-rooms
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Added support for PSTN Dial-Out Feature in ACS Rooms
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
Yes
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [X] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [X] Added a changelog (if necessary)
### Packages impacted by this PR
Health Insights CancerProfilingRest and ClinicalMatchingRest (new
packages).
### Issues associated with this PR
[[Cognitive Services - Health Decision Support] REST API Review · Issue
#5731 · Azure/azure-rest-api-specs-pr
(github.com)](https://github.com/Azure/azure-rest-api-specs-pr/issues/5731)
### Describe the problem that is addressed by this PR
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Provide a list of related PRs _(if any)_
[[Cognitive Services - Health Insights] CADL revision for public preview
by asaflevi-ms · Pull Request #22990 · Azure/azure-rest-api-specs
(github.com)](https://github.com/Azure/azure-rest-api-specs/pull/22990)
---------
Co-authored-by: Asaf Levi <asaflevi@microsoft.com>
Co-authored-by: Mary Gao <yanmeigao1210@gmail.com>
Fixes https://github.com/Azure/azure-sdk-for-js/issues/25058
### Packages impacted by this PR
@azure/monitor-query
### Issues associated with this PR
NA
### Describe the problem that is addressed by this PR
In this PR, a new client called `MetricsBatchClient` has been added to
the SDK. This Client is generated from this
[swagger](https://raw.githubusercontent.com/Azure/azure-rest-api-specs/5f700acd3d094d8eedca381932f2e7916afd2e55/specification/monitor/data-plane/Microsoft.Insights/preview/2023-05-01-preview/metricBatch.json).
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
The names of the following properties: `Metric`, `TimeSeriesElement`,
`MetricValue`, `MetadataValue` and `MetricUnit` are conflicting with the
existing names. So, they are renamed as `BatchMetric`,
`BatchTimeSeriesElement`, `BatchMetricValue`, `BatchMetadataValue` and
`BatchMetricUnit`.
### Are there test cases added in this PR? _(If not, why?)_
Since this is a beta release and needed to be released at the earliest
and the code has been tested locally, test cases are not added with this
PR. It will be added seperately
### Provide a list of related PRs _(if any)_
None
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
`...\azure-sdk-for-js\sdk\monitor\monitor-query> autorest --typescript
.\swagger\metric-Batch.md`
### Checklists
- [X] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [X] Added a changelog (if necessary)
@KarishmaGhiya @jeremymeng Please review and approve the PR.
@srnagar @scottaddie @xirzec FYI......
---------
Co-authored-by: Srikanta <51379715+srnagar@users.noreply.github.com>
Co-authored-by: Scott Addie <10702007+scottaddie@users.noreply.github.com>
This is the (internal/private) SDK for Tiering, currently, retrieves
limits for each capability (SMS/PSTN Calling/Phone Number purchasing)
for a specific resource/tier.
On a high level all of these endpoints are here to achieve that:
`Get acquired number limits` - how many numbers a resource has already
acquired and the limits
`Get tier info` - retrieving tier information for a resource
This pull request updates the SDK with the remaining V4 Media features,
including:
- Media Streaming
- Play TTS
- Play SSML
- Recognize choices
- Recognize speech
### Packages impacted by this PR
### Issues associated with this PR
### Describe the problem that is addressed by this PR
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
This PR introduces the @azure/ai-openai library. Please ignore the
`sources` folder for now. Also, please note that it has been decided to
use the REST names of the properties in the output models for this first
release, so although they don't sound like the best names, they will not
be renamed in this first release.
Also, please note this package is scheduled for release on 5/22.
---------
Co-authored-by: Jeremy Meng <jeremy.ymeng@gmail.com>
Add maxNumberOfJobs and WebhookRule
Fix swagger generation
Fix bunch of issues in RouterClient, RouterAdministrationClient and
models, options
Update Readmes
### Packages impacted by this PR
### Issues associated with this PR
### Describe the problem that is addressed by this PR
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
as the file mostly contains aliases and paths, with a handful comments.
There's little value spell-checking it. Also aliases will cause a lot of
noises. This PR excludes it from being checked.
### Packages impacted by this PR
@azure-rest/ai-translation-text
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Adding Translation Text Service SDK -
https://learn.microsoft.com/en-us/azure/cognitive-services/translator/reference/v3-0-translate
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
yes
### Provide a list of related PRs _(if any)_
ApiView -
https://apiview.dev/Assemblies/Conversation/929808949dbf4c0fb72a0b51de7ec395
TypeSpec -
https://github.com/Azure/azure-rest-api-specs/pull/23231/files
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
`tsp compile .`
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)
---------
Co-authored-by: Michal Materna <mimat@microsoft.com>
Co-authored-by: hamshavathimunibyraiah <125092972+hamshavathimunibyraiah@users.noreply.github.com>
Co-authored-by: Hamshavathi Munibyraiah (Murphy V-hmunibyrai Associates Inc) <v-hmunibyrai@microsoft.com>
Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com>
This PR ties up some loose ends in the Form Recognizer release.
- Updates the README with details about the new classification feature.
- Adds a `classifyDocument` sample.
- Regenerates `samples/v4-beta`.
- Slightly tweaks prebuilt codegen so that it adds
`@azsdk-skip-javascript` to prebuilt model code.
WIP
This PR updates @azure/ai-form-recognizer to support API version
`2023-02-28-preview`. It updates the SDK version to 4.1.0-beta.1.
It also removes the test recordings which have been onboarded to the
asset sync tool.
The changes are described in CHANGELOG.md. All generated files (prebuilt
models) have been regenerated based on the latest model schemas. The
vast majority of changes are deleted recordings or regenerated models.
See the `api.md` file for changes to the API.
### Packages impacted by this PR
- @azure/notification-hubs
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Adds Xiaomi support for Track 2 SDKs with registration, installation,
send and send outcome operations.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
yes
### Provide a list of related PRs _(if any)_
- https://github.com/Azure/azure-notificationhubs-dotnet/pull/261
- https://github.com/Azure/azure-notificationhubs-dotnet/pull/260
- https://github.com/Azure/azure-notificationhubs-dotnet/pull/259
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)
---------
Co-authored-by: Jeremy Meng <jeremy.ymeng@gmail.com>
### Packages impacted by this PR
@azure/web-pubsub-client-protobuf
This is the init pr for @azure/web-pubsub-client-protobuf. Please review the package name, dependencies.
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_
- [ ] Added a changelog (if necessary)
### Packages impacted by this PR
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Adding rest client package for Sharing service under Microsoft Purview
product group.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
Yes
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)
### Packages impacted by this PR
web-pubsub-client
### Issues associated with this PR
### Describe the problem that is addressed by this PR
This is the init PR for new package web-pubsub-client.
### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
### Are there test cases added in this PR? _(If not, why?)_
Yes
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_
- [x] Added a changelog (if necessary)
* Initial generation
* Remove unused dependency
* Add customize AAD authentication
* Add test cases
* Add a helper positionToTileXY
* Add samples
* add helper function: createPathQuery
* lineWidth -> lineWidthInPixels
* add helper: create pins query
refactor the helper function
* Add getMapStaticImage samples
* Add @example in typedoc for createPinsQuery
* Build samples
* Final refinement
* Update samples
* Update the recording with the fixed test proxy which support br encoding
* Fix several error from Build Analyze pipeline
- Add "bbox" as an exception for maps-rest api-view
- Remove locale info "en-US" in the link from README
* Fix format
* Fix typos
* Add TODO comment for collectionFormat: multi
* Fix the wrong snippet
* Make path support multi collectionFormat
* Make createPinsQuery support collectionFormat: multi
* Fix lint issue
* Update recording
* Add "require" in the code snippet in README
* Disable doc ms in samples
* [EventGrid] Update Healthcare Events, Prepare for Nov Release
The only updates for our November release are adding type interfaces
for two new healthcare API events which the service now sends.
* Add Dicom as an allowed word
* Update maps dependency in pnpm-lock.yaml
* Fix sample metadata errors
* Fix linting errors
* Fix linting errors
* Fix run time error
* Update package.json in samples folder
* Fix linting errors
* Fix linting errors
* Add changelog for maps-common
* Update recording files for maps-search
* Add test.yml for maps-search
* Add tests.yml for render and route
* Update tests.yml
* Update test-resources.json for maps
* Fix tests.yml format error
* Update env vars and remove unused export var
* Remove unused code
* Fix lock file
* Remove route & render
* Replace `beginGet*Batch` with `resume*Batch`
We provide a `beginGet*Batch` method to resume the previous
request previously. This is not ideal because it need to get a
`batchId` which is store in the internal state of the LRO. Once
the LRO brings changes, our code will be broken.
We can achieve the same thing by using serialized state.
This change aims to leverage this approach and create convenience
methods `resume*Batch` for users
* Update recording
* Make the endpoint of `MapsSearchClient` configurable
* Change LatLon from an interface to a tuple
Also remove the `toLatLon` function since creating a tuple
is quite easy.
* Make the props `coordinates` and `countryCodeFilter` optional
Specifying `coordinates` and `countryCodeFilter` can narrow the results
of the fuzzy search. But considring the case like searching "Australia",
theese fields may have no use. We decided to make them optional so user
can decides if they want to narrow down the results or not.
* fixup! Remove route & render
* Adjust CHANGELOGs of maps-search & common
Following the keyvault-common, removing CHANGELOGs
from maps-common since it's not published.
* Update samples
* Add batchRequest sample
* Add a new sample searchAddressResult
* Update search.ts and its examples
* enhance code example in README.md
* comment unused import
* Update recording for maps-search
* remove redundant recording files
* Add maps-search
* Rename LatLong to LatLon
* Fix constructor Readme doc
* Update readme to new signature
* Add tests partially
* Change LatLon/BoundingBox to interfaces
* Reduce the number of constructor overloading
* Rename SearchClient as MapsSearchClient
* Add options mapper tests
* Add result type mapper tests (in progress)
* rename clientId to mapsAccountClientId
* listPolygons -> getPolygons
* getPointOfInterestCategoryTree -> getPointOfInterestCategories
* Expose missing model
* Add alternative input file for quick experiment
* Regenerate code and make changes accordingly
* Reduce number of overloads of fuzzy searches
* Add geojson types
* Adopting new geojson definitions
* Change test specs to align with new method names
* clean up models and tsconfig
* Expose Known* models
* Remove batch sync methods
* Add public tests (non-batch)
* move model
* Add docstrings
* Start polling in begin* method
* Refactor BatchPoller for retrieving batchId
* Finalize batch pollers
* Readd batch methods
* Update generated code
* Finalize batch signature
* Rebuild samples & clean up
* Add AAD tests
* Clean up Swagger readme
* Fix spelling
* Add initial files for @azure/maps-route module
* maps-search: change comments and perform formatting
* Methods options and testing skeleton for maps-route
* maps-search: refactor options
* Improve convenience layer for non-LRO methods
* Change variable names
* Complete batch methods
* update maps-search Readme
* Update maps-route Readme
* Add generated samples for maps-route
* Update samples for maps-search
* Delete backup file
* Add maps-common module
* Update maps-route/maps-search to use maps-common
* maps-render: first draft
* Use LatLon/BoundingBox from maps-common
* Complete maps-render with tests
* Expose required types from maps-route
* Expose required types from maps-search
* Complete unit tests for maps-render
* Update maps-render README
* Update samples
* Fix comment/strings
* Fix comment/strings
* Update Route comment/interface
* Regenerate code
* Update files
* Define required fields and fix code
* Remove non-poller batch methods
* Fix playback test failure
* Rename parts of model names
* Rename remaining parts of models according to review feedback
* Remove TODO comments
* Update Reamdme transform to reflect latest swagger
* Change key policy name
* Simplify batch item error model
* Add brower tests
* Turn maps-common into internal module
* Rearrange Readme
* Rewrite Readme for common
* Remove batch-sync methods
* Route required fields: part 1
* Route required fields: part 2
* Add AAD back
* Route model fixes#1
* Route model fixes#2 + geojson named tuples
* Refine geojson types
* Aliased a few method options
* maps-render required fields part 1
* Do not validate budget parameters
* Revert "Do not validate budget parameters"
This reverts commit 4ec3f5fd18a21466745ad23fe3e79c043ace9546.
* Rename MapTileset to TileJson
* Render: model rename & type improvement
* Explicitly transform image range
* Fix route record tests
* Update map account creation commands in Readme
* Update Readme/docstrings/samples for Search/Route/Render
* Remove rollup and use dev-tool instead
* Remove some empty tests
* Add AAD test case and make file name shorter
* Update test cases
* Update cspell rules
* Update recording files
* Simplify test cases
* Sync cspell.json from upstream
* Use test-recorder 2.0 and update unit test cases
* Push wrong browsers recording files
* Update settings to support recording
* Fix dependency errors
* Upgrade api-recorder and fix errors
* Code refinement
* Update maps search recording files
* Update karma.conf.js format
* Update recording files and settings
* Fix broken links
* Update maps dependency in pnpm-lock.yaml
* Fix sample metadata errors
* Fix linting errors
* Fix linting errors
* Fix run time error
* Update package.json in samples folder
* Fix linting errors
* Fix linting errors
* Add changelog for maps-common
* Update recording files for maps-search
* Add test.yml for maps-search
* Add tests.yml for render and route
* Update tests.yml
* Update test-resources.json for maps
* Fix tests.yml format error
* Update env vars and remove unused export var
* Remove unused code
* Fix lock file
* Remove maps-render
* fixup! Change LatLon from an interface to a tuple
* Comment the future doc link
* Update doc & fix type issue
* fix lint issues
* Regenerate API View
* Comment the whole [apiref] since the original syntax cannot pass the Analyze/Link verification
* Fix issue related to the change of maps-common
- Replace beginGet*Result with resume* methods
- Turn LatLon to a tuple
- Add mapper to transform the string to Date because resume* method will
return a serialized Date
* Update test recording
* Remove maps-common from the Artifacts
* remove unused dependencies
* Add impression in README so we can track the page views
* Remove `AZURE_LOG_LEVEL` in test.yml
* Update samples
- Move the option parameter to the right place
- Add comments & "break" for handling the type of the search result to make it clear for the user
* Patch {} to properties for GeoJsonPolygon
* rename maxDetourTime to maxDetourTimeInSeconds
* Update recordings
* Remove any
* Rename to detourTimeInSeconds to align the convention
* Change the test.yml EnvVar
See more explanation here:
- https://github.com/Azure/azure-sdk-for-js/pull/23039#discussion_r973292952
- https://github.com/Azure/azure-sdk-for-js/pull/23039#discussion_r972413976
* Rename numResults to numberResults
* Add document comment
* Add endpoint options to MapsRouteClient
* Remove unused dependencies in maps-route
* fixup! Change the test.yml EnvVar
* Update interfaces & documents
* Update changelog
* Merge getRouteDirection with the additional parameter one
* Update samples
* Make the `maps-common to a published package
* Update the import of `maps-common` in `maps-search`
* Fix CI Issue
* Add documents for geojson
* Update the samples & readme
* Leverage maps-common package in mpas-route
* chore update
- Remove the unnecessary rule setting of eslint
- Update the legacy type path
* Remove unnecessary eslint config
* WIP: Remove LRO generation
* WIP: refactor mapsRouteClient
* WIP: first generation
* Format the generated code
* Support AAD
* Transform the model name
* Add helper functions
* Add a sample - route.ts
* Add samples for lro
* Add test
* Generate samples
* Add api view
* Update the generation
* WIP: ReadMe
* Rename "computeBestOrder" to "computeBestWaypointOrder"
* Refine README
* Rename model
* Add test createRouteDirectionsBatchRequest
* Fix lint issue
* Add missing metadata
* Remove maps-route/
* Update CI issue
* Fix merged issue
* Update version rule for maps-common
* Update CI name
* Remove extra lint config
* Use `require` in the README for consistency
* Regenerate the samples
* Remove redundant recording files
* Remove unused parameters in test-resources.json
* Refine readme snippet
* Log something specific for the result
* Update samples
* Split the route.ts into 3
* Remove model rename
* Use default export for RLC factory function
Co-authored-by: Charlie Chen <charlie.chen@microsoft.com>
Co-authored-by: Charlie Chen <yuchungchen@microsoft.com>
Co-authored-by: --global <alankashiwa@gmail.com>
danielszaniszlo
Maor Leger
Sarangan Rajamanickam
Daniel Getu
chungshengfu
v-durgeshs
koen-mertens
Yifan Zhou
Matthew Podwysocki
Deyaaeldeen Almahallawi
Glenn Harper
Franko Morales
minwoolee-msft
Andrew Kao
Harsha Nalluru
Jeremy Meng
Scott Addie
Mike Hang
reutgross
Hector Hernandez
classBabacar-msft
Adam Tazi
williamzhao87
Michal Materna
Will Temple
Chenyang Liu
Anniruddh K
Chenyang Liu
Timo van Veenendaal
Matt Ellis
Mrinal Gautam