-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linting + Formatting #193
base: master
Are you sure you want to change the base?
Linting + Formatting #193
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
As a side note, https://www.moxio.com/blog/43/ignoring-bulk-change-commits-with-git-blame explains how you can ignore this commit in the future for git blame
.
@@ -0,0 +1,58 @@ | |||
# Vimari Setup |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would call this file DEVELOPERS.md
Some more detail about the linting & formatting setup should be included, I came by this readme which is a bit more specific about setup. Will try to include something similar. |
To improve the workflow for contributors this PR introduces both linting and formatting of code to the repo. The tools used are explained in
SETUP_README.md
which I plan to expand upon with more setup instructions.Two Github workflows have been added that only run on relevant pull requests for linting and formatting either JavaScript code or Swift code.
Lots of changes have been made to make the current code adhere to the default styles enforces by the chosen tools (see #179). I suggest we squash all the commits during the merging process.