This repository was archived by the owner on May 26, 2024. It is now read-only.
Shirotohu update codestyle #25
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this? (check all applicable)
Description
I have just updated the code style to account for documentation styles. This will help me write the documentation and keep it consistent as well. It's a good reference.
Note
I the code style I wrote a little bit of a reference as to the styling of the parameter, attribute and method documentation. I think this could use some work, but since I am the only contributor, for the time being it should be alright.
Added changes
Note
I also want to point out that I understand when writing the documentation, we kind of want to use the signature of whatever we are documenting with their types etc. This isn't present present in the code style markdown file. I might create an issue and put it in the backlog, while we focus on other things.
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
Please replace this line with instructions on how to test your changes, a note
on the devices and browsers this has been tested on, as well as any relevant
images for UI changes.
Added/updated tests?
We encourage you to keep the code coverage percentage at 80% and above.
Checklist