This PR adds a pre-commit check and formatting step leveraging pyproject-fmt to help standardize the formatting found within the file, similar to how black or ruff-format work with Python code.
Additionally - I moved inline comments for dependencies to be above their related lines (to conserve line space) and updated the version of the project to be in alignment with dynamic versioning (0.0.0).
What kind of change(s) are included?
[ ] Documentation (changes docs or other related content)
[ ] Bug fix (fixes an issue).
[x] Enhancement (adds functionality).
[ ] Breaking change (these changes would cause existing functionality to not work as expected).
Checklist
Please ensure that all boxes are checked before indicating that this pull request is ready for review.
[x] I have read and followed the CONTRIBUTING.md guidelines.
[x] I have searched for existing content to ensure this is not a duplicate.
[x] I have performed a self-review of these additions (including spelling, grammar, and related).
[x] These changes pass all pre-commit checks.
[ ] I have added comments to my code to help provide understanding
[ ] I have added a test which covers the code changes found within this PR
[x] I have deleted all non-relevant text in this pull request template.
Thanks @jenna-tomkinson ! I've created an issue for the versioning item (I don't believe there's any additional configuration we need at this time). Merging this in.
Description
This PR adds a pre-commit check and formatting step leveraging
pyproject-fmt
to help standardize the formatting found within the file, similar to howblack
orruff-format
work with Python code.Additionally - I moved inline comments for dependencies to be above their related lines (to conserve line space) and updated the version of the project to be in alignment with dynamic versioning (
0.0.0
).What kind of change(s) are included?
Checklist
Please ensure that all boxes are checked before indicating that this pull request is ready for review.