-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add MLJ compliant doc-strings - take II #23
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #23 +/- ##
==========================================
- Coverage 88.04% 87.76% -0.28%
==========================================
Files 7 8 +1
Lines 184 188 +4
==========================================
+ Hits 162 165 +3
- Misses 22 23 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Yes I will take a look this week! Thanks! |
@pazzo83 Do you still have some time to look over this? |
I am going to try to look at it this weekend!
…On Thu, Sep 22, 2022 at 12:16 AM Anthony Blaom, PhD < ***@***.***> wrote:
@pazzo83 <https://github.com/pazzo83> Do you still have some time to look
over this?
—
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACDUZUJYSCFXOHDA6UN36Q3V7PMSVANCNFSM6AAAAAAQETMVAA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Again sorry for the delay here! This looks good! Should I merge? |
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 great! We might need to update some of the package versions in requirements?
I've kicked CompatHelper out of hibernation and all looks good. |
Replaces #22
@pazzo83 I have a reviewed the original PR, to ensure compliance with the new MLJ standard, but have also made some changes of my own (which involve some paring down of your original strings). Would you have time in the next few weeks to do a final review?
I suggest one begins by looking over the final docstrings generated by a
julia> ?
query, as some of the interpolation magic makes it hard to catch all mistakes by just reading code.cc @josephsdavid