modified readme of [DocumentIntelligence] wrong import of AnalyzeOper… #32412
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.
…ationOutput. changes in changelog, samples and release note for GA 1.0.0 #32326
Packages impacted by this PR
Azure Documentintelligence
Issues associated with this PR
Fixed wrong import of AnalyzeOperationOutput
Describe the problem that is addressed by this PR
Previously in the readme of Azure DocumentIntelligence (formerly FormRecognizer) REST client library for JavaScript in Continue creating the poller from initial response section the import of AnalyzeOperationOutput was wrongly added as AnalyzeResultOperationOutput in 3 counts that has been modified.
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?
It was the only simple solution
Are there test cases added in this PR? (If not, why?)
No just modified readme to update documentation of wrong import
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists