-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[FR] Samples for DMAC #24300
[FR] Samples for DMAC #24300
Conversation
API changes have been detected in this PR. You can review API changes here |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very straightforward. LGTM.
@@ -0,0 +1,57 @@ | |||
// Copyright (c) Microsoft Corporation. All rights reserved. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
File name has a typo: Asyncs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changos!!!!
sdk/formrecognizer/Azure.AI.FormRecognizer/tests/samples/SampleSnippets.cs
Show resolved
Hide resolved
sdk/formrecognizer/Azure.AI.FormRecognizer/tests/samples/Sample_CreateComposedModelAsync.cs
Show resolved
Hide resolved
API changes have been detected in this PR. You can review API changes here |
@@ -402,191 +210,23 @@ For more information and samples using prebuilt models see: | |||
### Train a Model |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Build a Model ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not making modifications to the Readme in this PR. Will do in a future PR
@@ -402,191 +210,23 @@ For more information and samples using prebuilt models see: | |||
### Train a Model | |||
Train a machine-learned model on your own form types. The resulting model will be able to recognize values from the types of forms it was trained on. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should be changing this line too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not making modifications to the Readme in this PR. Will do in a future PR
Console.WriteLine($" Lower left => X: {selectionMark.BoundingBox[3].X}, Y= {selectionMark.BoundingBox[3].Y}"); | ||
} | ||
} | ||
``` | ||
For more information and samples see [here][recognize_content]. | ||
|
||
### Recognize Custom Forms |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Analyze Custom Documents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not making modifications to the Readme in this PR. Will do in a future PR
@@ -185,121 +185,11 @@ The following section provides several code snippets illustrating common pattern | |||
### Recognize Content | |||
Recognize text, tables, and selection marks like radio buttons and check boxes data, along with their bounding box coordinates, from documents. | |||
|
|||
```C# Snippet:FormRecognizerSampleRecognizeContentFromUri |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will you be adding samples in a later PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. When I work on the Readme, I will add the real samples here
@@ -20,7 +20,7 @@ You can set `endpoint` and `apiKey` based on an environment variable, a configur | |||
### Source client | |||
The source client that contains the custom model we want to copy. | |||
|
|||
```C# Snippet:FormRecognizerSampleCreateCopySourceClient | |||
```C# Snippet:FormRecognizerSampleCreateCopySourceClientV3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if V3 would be appropriate, should we use the date version for the folder name?
And would that be enough without having to append the V3 in FormRecognizerSampleCreateCopySourceClientV3
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in this case, V3 is reflecting the SDK version. It is following the structure we talked about of having samples in V3 folder and current samples in either a V4 folder or in the main samples folder.
Although snippet strings are internal to us, they are the way for us to know where the code for the sample lives. We have also modified the samples code and moved all "old" samples to a V3 folder
https://github.com/Azure/azure-sdk-for-net/tree/feature/formrecognizerv4/sdk/formrecognizer/Azure.AI.FormRecognizer/tests/samples
Do you think this is clear enough for future developers to know which code/snippet/sample, lives where?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm... I feel v3 or v4 is awkward since we havent used these terms before. Could we use similar wording as what python did v3.1
and v3.2-beta
Do you think this would be better?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like it! I will change it to v3.1
everywhere to make it more clear. I will do it in the next PR to keep this one "small-ish"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need samples for get/list operations?
Great point. I will add them here |
API changes have been detected in this PR. You can review API changes here |
sdk/formrecognizer/Azure.AI.FormRecognizer/tests/samples/Sample_ManageOperationsAsync.cs
Outdated
Show resolved
Hide resolved
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them. In order to bootstrap pipelines for a new service, please perform following steps: For data-plane/track 2 SDKs Issue the following command as a pull request comment:
For track 1 management-plane SDKsPlease open a separate PR and to your service SDK path in this file. Once that PR has been merged, you can re-run the pipeline to trigger the verification. |
API changes have been detected in this PR. You can review API changes here |
To avoid conflicts I removed all code snippets from the main Readme and I renamed some of the snippets to include
V3
at the end. I want to make sure I don't use them by mistake.This PR has
async
samples. After this PR I will create thesync
ones and the respective.md
files.