-
Notifications
You must be signed in to change notification settings - Fork 1.9k
API reference - XML documentation template for transforms #3204
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
Comments
I'd suggest to document |
Referencing #3127 as this feels same or related, maybe we could track this work under one issue? I think there are going to be a number of subsections that will need to be tracked. And should this go on the transforms? Or the extensions? |
It won't work, because GetOutputSchema is on the base class, and is calling GetOutputSchemaCore of every class, which is internal. |
Proposal for the transforms XML template, mirroring the trainers template from issue: #3218, 1- XML on Transform extension method:
2 - XML of the Estimator, Transformer
|
Looks good @sfilipi. One small comment: for the summary of the extension method, would we want to say: "Create an xxx transform ..."? |
Shouldn't it say "Create an xxx estimator" instead of "transform"? |
@natke suggested that we reference the components by their functionality: trainers and transforms. in the Remarks of the actual estimator we're keeping transform, as a term. |
|
Transform priority is in this old issue. Use it as guide to prioritize more popular transforms. Also, reuse descriptions from here. List of transforms to sign up for:
|
Other catalogs:
For the Data catalog, all API's documentations needs to be augmented with suggestions for when would one use this API.
|
* applying the dotnet#3204 template to ColumnCopying.
Tracked in dotnet#3204
…ator (#3384) * Documentation for FeatureContributionEstimator * Address code review comments * Address code review comments
* XML documentation for Normalizer Tracked in #3204
Finished 4/21 9:29pm. Great team work. |
The XML documentation for the transforms should contain information about the schema: requirements about the type of the columns to work on, and information about the type of the columns produced.
@shmoradims
The text was updated successfully, but these errors were encountered: