-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: Updating str_slice docstring #22569
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
DOC: Updating str_slice docstring #22569
Conversation
Codecov Report
@@ Coverage Diff @@
## master #22569 +/- ##
==========================================
- Coverage 92.19% 92.18% -0.01%
==========================================
Files 169 169
Lines 50833 50823 -10
==========================================
- Hits 46863 46853 -10
Misses 3970 3970
Continue to review full report at Codecov.
|
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.
Nice changes!
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.
Nice changes, added some comments about formatting and ideas to make the docstring even better.
@JesperDramsch do you have time to update this PR based on the comments? |
Totally missed this one. I'll get to it asap |
Hello @JesperDramsch! Thanks for updating the PR.
Comment last updated on October 03, 2018 at 21:27 Hours UTC |
Here we go. Ran validation and updated everything according to the comments and linter. Thank you for the comments @datapythonista and thanks for the patience @jorisvandenbossche. |
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.
lgtm, thanks for another great docstring @JesperDramsch
The build is broken now, but will merge once it's fixed and the checks are green.
@JesperDramsch can you rebase, so the CI runs again, and we can merge it? |
I'm not really sure what that means. How do I rebase? |
Sorry, we use rebase as short for updating your PR with the latest master. Just run in your branch: This is usually required when the branch of the PR has conflicts with master. In this case github would manage the merge itself, as there are no conflicts. But as the checks of the CI failed (for reasons unrelated to your PR), we just want them to run again. And as there are many systems, and I don't thing I even have permissions to all them, the easiest is that you update your branch, and then all them are automatically rerun. With some luck we'll make things easier soon. :) |
Alright. I can get to that tomorrow easily. |
@JesperDramsch seems like there is a formatting issue Can you fix it please. Happy to merge it afterwards. |
Aw Yiss. |
Thanks for another great docstring @JesperDramsch |
Added Examples to docstring.
Added documentation to each part of docstring