Repository navigation
docs: explain per-model null handling in target - #141
Merged
geetu040 merged 1 commit intoNov 3, 2026
Merged
Conversation
Signed-off-by: Ahmed Samaila <ahmaduahmadu234@gmail.com>
geetu040
approved these changes
Nov 3, 2026
geetu040
left a comment
Member
There was a problem hiding this comment.
Thanks for the contribution, this looks good.
Contributor
Author
|
Thanks @geetu040 for the review and merge. Happy to help with follow-up docs if useful. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #140 (docs part).
Adds a short section to
docs/client/data.mdexplaining that null handling in the target depends on each sktime estimator'scapability:missing_valuestag, with a link to https://www.sktime.net/models. Requested by @geetu040 on #140.