-
-
Notifications
You must be signed in to change notification settings - Fork 26k
DOC: Fixes Docs for estimator types do not list all possible estimator types #29956
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
bf103ea
After pre-commit
DeaMariaLeon b46a14e
Merge remote-tracking branch 'upstream/main' into develop-doc
DeaMariaLeon d105a7d
DOC: Adding estimator types
DeaMariaLeon 9d2b5db
Merge remote-tracking branch 'upstream/main' into develop-doc
DeaMariaLeon 10278ac
added links to classes, corrected one class name
DeaMariaLeon 6cdcf64
Merge remote-tracking branch 'upstream/main' into develop-doc
DeaMariaLeon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I agree that this matches our current code base; however, I find the casing style of the last tag value inconsistent with the others. However, I don't see any easy way to fix it without breaking backward compat because it's technically part of our public API.
I guess we have to live with it for now but keep it in mind if we want to release scikit-learn 2.0 one day.
/cc @adrinjalali as developer API specialist.
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.
in a rework of this document, I'd like to remove all of these and only document developing estimators via inheriting from our mixins. That would remove these parts anyway.
Otherwise. also gonna work on a PR to move this from the class attribute to a tag. I think it's doable, but need to actually implement it to be sure.
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.
I like the fancy title 😅