Repository navigation
System.MachineLearning.Runtime namespaces cleanup #18
Description
From @KrzysztofCwalina on Apr 16, 2018, 9:11 AM PDT
There are several problems with System.MachineLearning.Runtime namespaces. We should clean these problems out:
-
There are too many System.MachineLearning.Runtime subnamepsaces. This will overwhelm users browsing the documentation on MSDN, IDE browsers, etc. We should combine the APIs in fewer subnamespaces.
-
We should not use "Api" in namespace or project names. All public things are "APIs" as far as .NET developers are concerned.
-
We have "EntryPoints" namespace. We should rename it. All "entry point" APIs should simply be in the root namespace (or subnamesapce of the root..
-
We should not have "tools" APIs in the main assmebly. Remove/rename Microsoft.MachineLearning.Runtime.Internal.Tools
Activity
shauheen commentedon Jun 28, 2018
This work may need more hashing specially in light of the API work. I will keep the issue for now. we will revisit after 0.4.
abgoswam commentedon Oct 15, 2018
DRI RESPONSE : moving to 0.7 (awaiting triage) probably requires splitting into multiple issues
shauheen commentedon Nov 27, 2018
With the API plans runtime will be removed, so this should not be valid anymore.
make GetNextPipeline API w/ public Pipeline method on PipelineSuggest…
code migration from machinelearning-automl to machinelearning repo fe…
make GetNextPipeline API w/ public Pipeline method on PipelineSuggest…