-
Notifications
You must be signed in to change notification settings - Fork 1k
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]: Add docstring example to the contributing docs #2254
Conversation
What do we think about these directives? https://www.sphinx-doc.org/en/master/usage/restructuredtext/directives.html#describing-changes-between-versions I rather like them but don't want to introduce something that's a pain to manage. If we like them, it would be nice to show one in the example. |
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 job. I think this example will certainly help contributors in the future
where :math:`a` is the result of the equation, :math:`b` and :math:`c` | ||
are inputs. | ||
|
||
Or a figure with a caption: |
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.
Is it worth adding somewhere where such figures should be stored in the pvlib directory?
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.
I think that is intuitive enough if you see the repo layout and that most of the time us contributors copy&paste from other places. Feel free to weight in 👀
Co-Authored-By: RDaxini <[email protected]>
Co-Authored-By: Adam R. Jensen <[email protected]>
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.
Personally this is exactly what I had in mind when we were discussing this! Nice work @echedey-ls! Some suggestions from my side.
Co-Authored-By: Ioannis Sifnaios <[email protected]>
Co-Authored-By: Ioannis Sifnaios <[email protected]>
Co-Authored-By: Ioannis Sifnaios <[email protected]>
Co-Authored-By: Adam R. Jensen <[email protected]> Co-Authored-By: Ioannis Sifnaios <[email protected]>
Co-authored-by: Cliff Hansen <[email protected]>
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.
This looks great to me. I bet an example like this will be a good reference not just for pvlib, but other packages too, and even people's personal code.
Thanks @echedey-ls and all reviewers :) |
docs/sphinx/source/whatsnew
for all changes. Includes link to the GitHub Issue with:issue:`num`
or this Pull Request with:pull:`num`
. Includes contributor name and/or GitHub username (link with:ghuser:`user`
).remote-data
) and Milestone are assigned to the Pull Request and linked Issue.Adds a docstring example to the contributing page. Now that I came back to the conversation in #2081 I see it was a discussion between @IoannisSifnaios and @AdamRJensen , so sorry for getting into it.
I still hesitate a bit on whether this is the preferred format to include this template here, maybe just linking to well documented functions is enough.