Add automated test to check for any eslint/prettier issues that need to be fixed #63
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: profectus/Profectus#63
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Would help keep the code style more consistent, since not everyone has the "run prettier on save" setting on their IDE.
Alongside this, proper contribution guidelines should probably be written somewhere that mentions running prettier on any changed files is expected and required before a PR gets merged. It could also mention bug fixes require a regression test to be written that fails without the fix and passes with the fix.