Request for Code Formatting Standardization in Project: Configuring a Formatter for Consistent Code Style

[ebenezer-melkamu]

Is your feature request related to a problem? Please describe.
VS-Code formatters are inconsistently leaving a trailing comma in object lists. This leads to "flip-flopping" between two practices when submitting PRs.

Including a formatter/prettifier config in the repo will ensure that VS-Code provides consistent formatting on "format on save".

There is no prettier.rc file in the codebase, and the current editorconfig formatter setup is not overriding the configuration i have in my local machine

Describe the solution you'd like
Add a .prettier.rc file in the codebase and then put the code formatting setup there

[IanMayo]

Hey @AbegaM - now is a great time to implement this, we have no open PRs.

Do you have any requirements/preferences to contribute to this @thevahidal ?

[thevahidal]

Hey @IanMayo,
Right now we have Prettier (and eslint) hooked in pre-commit (using husky and lint-staged, refer to

soul/package.json

Lines 67 to 70 in 5bbd1a0

	"lint-staged": {
	"*.js": "eslint --fix",
	"*.{js,css,md,html,json}": "prettier --write"
	}

), and also it worths mentioning that we're also using eslint-config-prettier which turns off all eslint rules that are unnecessary or might conflict with Prettier. Again all these happen when someone tries to commit something.

Since Prettier is an opinionated formatter and it has a decent set of defaults, I think it's a good idea to keep using its defaults but tweak the ones we don't like.

I'm open to any suggestions, let me know what you think!