-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Command-line oriented arguments, that have more suitable alternatives for the API should be made internal #2133
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
The other two occurrences of this are: CustomStopWordsRemovingTransform.ArgumentsBase public abstract class ArgumentsBase
{
[Argument(ArgumentType.AtMostOnce, HelpText = "Comma separated list of stopwords", Visibility = ArgumentAttribute.VisibilityType.CmdLineOnly)]
public string Stopwords;
[Argument(ArgumentType.AtMostOnce, HelpText = "List of stopwords", Visibility = ArgumentAttribute.VisibilityType.EntryPointsOnly)]
public string[] Stopword; and public sealed class TermLoaderArguments
{
[Argument(ArgumentType.AtMostOnce, HelpText = "Comma separated list of terms", SortOrder = 1, Visibility = ArgumentAttribute.VisibilityType.CmdLineOnly)]
public string Terms;
[Argument(ArgumentType.AtMostOnce, HelpText = "List of terms", SortOrder = 1, Visibility = ArgumentAttribute.VisibilityType.EntryPointsOnly)]
public string[] Term; |
I would say that the name |
After further investigating, it seems that the above Arguments classes should be made internal. They are only used by the entrypoints API. We are using other objects to set the parameters of the estimators (either direct definition of the parameters in the constructors, or through a ColumnInfo object). |
The only transform that still has public Options class (former Arguments class) is the The remaining transform either use the This issue can therefore be considered closed. |
In the arguments classes there are several arguments that get translated to the same parameter for the estimators/transforms.
One of the variant is a convenience for the command line version of ML.Net.
I think those can be made internal, and kept away from the user for v1.
Example:
ValueToKeyMappingTransformer.ArgumentsBase
I don't think our API users should see the first
public string Terms
The text was updated successfully, but these errors were encountered: