-
Notifications
You must be signed in to change notification settings - Fork 38
Ensure accepted input types are general where possible #480
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
Conversation
Codecov ReportBase: 68.81% // Head: 79.54% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #480 +/- ##
===========================================
+ Coverage 68.81% 79.54% +10.72%
===========================================
Files 52 52
Lines 1347 1354 +7
===========================================
+ Hits 927 1077 +150
+ Misses 420 277 -143
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: David Widmann <[email protected]>
…com/JuliaGaussianProcesses/KernelFunctions.jl into wct/generalise-accepted-input-types
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.
Looks good to me. I think the coverage comments by codecov are wrong?
Summary
As discussed in #479 , some of our kernels / transforms etc is overly strict in terms of the types that it accepts, prompting users to find workaround. The goal of this is to resolve these problems and add some tests to prevent regression.
Proposed changes
What alternatives have you considered?
N/A
Breaking changes
N/A