Thank you for considering to contribute to this project!
The following is a set of guidelines and resources for contributing to Auraxium.
-
Follow the official Python style guide PEP 8
-
Type hint your code according to PEP 484.
You must annotate any public members (e.g. method arguments, return values or attribute types).
It is also recommended to annotate any internal generics to help with catching errors, as well as to make it easier for others to understand your code.
Finally, use the broadest applicable generic type for your arguments, i.e. the least restrictive protocol.
Example: If your function only has to iterate over the argument, use
Iterable. If it also has to access its members by index, useSequence.Only use the more restrictive type
Listif you require list-specific methods like.append()or.clear().Refer to the Mypy docs for more information.
This project is documented in three places:
-
Every public class or method must be documented in the source code via docstrings.
-
Release-specific documentation, such as the public API, is dynamically generated from the source code and hosted on Read the Docs.
-
Release-agnostic documentation, like guides, tutorials and references, live in the GitHub Wiki instead.
This project uses the unittest testing framework for code validation.
The repository does have a workflow set up that will run unittest over any files matching <module>_test.py in the tests/ directory. Add your own tests there and they should be picked up just fine.
Feel free to add development tools to the tools/ directory, just make sure your tools are themselves well-documented, easy to use and provide some utility to other users.