-
Notifications
You must be signed in to change notification settings - Fork 370
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
TemplateVerifier docs #5510
TemplateVerifier docs #5510
Conversation
0e49c28
to
397b0d3
Compare
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.
Looks good. Probably we can also kick off the folder for authoring tooling, and also move localization article there.
TemplateSpecificArgs = new[] { "--arg1", "true" }, | ||
}; | ||
|
||
VerificationEngine engine = new(_logger); |
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.
it would be good to have an overload from XUnit logging 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.
Currently the API is intentionaly agnostic on the testing frameworks (under the hood it uses Verify.Xunit
, but just because the Verify functionality is currently surfaced only through 'protocol specific packages', however XUnit is neither enforced nor surfaced anywhere).
E.g. this specific code sample is in MSTest
Solution
Doc content for the TemplateVerifier feature #3868
Checks: N/A
#nullable enable
to all the modified files ?