[Form Recognizer] Update perf test to use latest FR #25680
Merged
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
HarshaNalluru
requested review from
witemple-msft,
deyaaeldeen,
ckairen and
jeremymeng
as code owners
deyaaeldeen
reviewed
Apr 27, 2023
sdk/formrecognizer/perf-tests/ai-form-recognizer/test/custom.spec.ts
Outdated
Show resolved
Hide resolved
… harshan/issues/25574
minhanh-phan
pushed a commit
to minhanh-phan/azure-sdk-for-js
that referenced
this pull request
Jun 12, 2023
Updates the perf test to use 4.0 version of the library by following the migration guide from v3 to v4 Fixes Azure#25574
azure-sdk
pushed a commit
to azure-sdk/azure-sdk-for-js
that referenced
this pull request
Sep 6, 2023
add JS and JAVA for Content Safety 0430 (Azure#25680) * add sdk java * Update tspconfig.yaml
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.
Updates the perf test to use 4.0 version of the library by following the migration guide from v3 to v4
Fixes #25574