-
Notifications
You must be signed in to change notification settings - Fork 88
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
Adding code documentation #186
Comments
@petergthatsme I would like to take a stab at this issue. Could you assign it to me? |
Hi Peter, I can also add documentation to the codes. Will you please add me? |
hey I'm interested , |
Just to clarify the rules of unitaryHACK (https://unitaryhack.dev/project-guide/): anyone is welcome to work on open issues, until they are closed. Issues do not need to be assigned to volunteers by maintainers before a pull request is approved (they can, but it's not required, and should not discourage other folks from participating). Thanks all for your interest! |
Congrats @WingCode for the successful hack! @petergthatsme Nice work with the actionable bounty as well. Please ensure @WingCode is the only assignee to this issue so our systems know he should be rewarded. |
We would like to add more complete documentation to the scqubits source code.
Here we ask for documenting signatures of 15 items such methods, functions, classes, etc, where the details are either incomplete, or missing completely.
Documentation should follow standards observed by the rest of the code.
Alternatively, fixing type annotation shown by rynning
mypy .
in the main folder would also qualify towards this goal.The text was updated successfully, but these errors were encountered: