Skip to content

[DOC] Docstring n code guideline #488 #505

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 5 commits into from
Jul 28, 2019

Conversation

shandou
Copy link
Collaborator

@shandou shandou commented Jul 28, 2019

PR Description

This PR contains the following additions to CONTRIBUTING.rst:

  • Guidelines and examples for docstring style
  • Guidelines and examples for code patterns
  • Guidelines and examples for example-based unit tests

This PR resolves #488.

PR Checklist

Please ensure that you have done the following:

  1. PR in from a fork off your branch. Do not PR from <your_username>:master, but rather from <your_username>:<branch_name>.
  1. If you're not on the contributors list, add yourself to AUTHORS.rst.

Sorry, but I don't see the CHANGELOG.rst file. Where is it?
3. [ ] Add a line to CHANGELOG.rst under the latest version header (i.e. the one that is "on deck") describing the contribution.
- Do use some discretion here; if there are multiple PRs that are related, keep them in a single line.

Quick Check

To do a very quick check that everything is correct, follow these steps below:

  • Run the command make check from pyjanitor's top-level directory. This will automatically run:
    • black formatting
    • pycodestyle checking
    • running the test suite
    • docs build

Once done, please check off the check-box above.

If make check does not work for you, you can execute the commands listed in the Makefile individually.

Documentation Changes

If you are adding documentation changes, please ensure the following:

  • Build the docs locally.
  • View the docs to check that it renders correctly.

Relevant Reviewers

Please tag maintainers to review.

Notes to reviewer:

Apologies for taking so long! I am not sure if my doc changes are a bit too detailed. When reviewing, please also check if there are any English issues and correct them as you go (I am not a native speaker). And please do not hesitate in providing feedback!

Thanks a lot! 😃

@codecov
Copy link

codecov bot commented Jul 28, 2019

Codecov Report

Merging #505 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #505   +/-   ##
=======================================
  Coverage   92.84%   92.84%           
=======================================
  Files           9        9           
  Lines         838      838           
=======================================
  Hits          778      778           
  Misses         60       60

Copy link
Member

@ericmjl ericmjl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shandou this is extremely high quality documentation! Thank you for your contribution! 😄


.. code-block:: python
:linenos:
:emphasize-lines: 1,2,7
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Superb! 😄 👍


Submit Feedback
~~~~~~~~~~~~~~~
-----------------
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor formatting suggestion: RST linters will usually make noise about the number of characters used to denote the header needing to match the number of characters in the heading text.

Suggested change
-----------------
---------------

@ericmjl ericmjl merged commit f5c21d0 into pyjanitor-devs:dev Jul 28, 2019
@hectormz
Copy link
Collaborator

This is great @shandou !

@shandou shandou deleted the docstring_n_code_guideline-#488 branch July 29, 2019 05:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[DOC] Docstring style should be made clear in contributing page
3 participants