Add automated test to check for any eslint/prettier issues that need to be fixed #63

Closed
opened 2024-02-14 20:17:25 +00:00 by thepaperpilot · 0 comments
Collaborator

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.

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.
thepaperpilot added this to the Automated Testing project 2024-02-14 20:17:31 +00:00
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: profectus/Profectus#63
No description provided.