You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
SamplesUtils is not searchable on doc site and makes ML.NET learning curve sharp #2794
We use SamplesUtils project in many examples. However, its functions and classes cannot be found in ML.NET's official doc site. This is not ideal because once a user has a question regarding SamplesUtils when learning our API examples, they will be blocked until they clones ML.NET or finds the right nuget package. This makes the learning curve of ML.NET very sharp. Also, please do not expect users have Visual Studio installed, so finding the right solution can be even more painful.
changed the title [-]SamplesUtils is not searchable on doc site[/-][+]SamplesUtils is not searchable on doc site and makes ML.NET learning curve sharp[/+]on Feb 28, 2019
I think we need clarification on how we should be formatting docs samples in this project, and what the relationship between the documentation samples and the samples.
Questions:
Should the samples included in the API docs be stand-alone, full length programs?
Should the samples included in the API docs be searchable on the docs site and live in their own section?
For question 2, please note that this issue was not about the sample code being searchable, but SamplesUtils namespace and it's utility classes being searchable. Sample code is not part of ML.NET API, so it's not searchable through API search.
Activity
[-]SamplesUtils is not searchable on doc site[/-][+]SamplesUtils is not searchable on doc site and makes ML.NET learning curve sharp[/+]rogancarr commentedon Mar 1, 2019
@CESARDELATORRE @JRAlexander
I think we need clarification on how we should be formatting docs samples in this project, and what the relationship between the documentation samples and the samples.
Questions:
Related to #2726
shmoradims commentedon Mar 1, 2019
I checked with Wei-Sheng and the APIs are searchable in API search.
@rogancarr let's discuss your question 1 above in #2726.
For question 2, please note that this issue was not about the sample code being searchable, but
SamplesUtilsnamespace and it's utility classes being searchable. Sample code is not part of ML.NET API, so it's not searchable through API search.Creating a `Rows` property, similar to `Columns` (dotnet#2794)
Move DataFrame to machinelearning (#5641)
Merge from main repository (#1)
Actually merge from main (#2)
Update editor config and format samples (#5893)