To ensure everyone is using the same coding standards and syntax, I added a settings.json to the project root. Make sure to have the prettier and eslint extensions installed in vscode. My hope is this will keep our code consistent and minimize unnecessary diffs in git (for example, changing of quotes, semi-colons or tab spaces)
I also installed a package to organize tailwind classnames in accordance to their documentation and opted to use es6 import modules in the backend to stay consistent with these standards and removed some boilerplate files. I moved the products array into its own constants file to clean up backend/index.js so we can have dummy data in that file for testing purposes.
Additional info
May need to verify that the eslint and prettier configs are working correctly in your remote workspace
What was done
To ensure everyone is using the same coding standards and syntax, I added a settings.json to the project root. Make sure to have the prettier and eslint extensions installed in vscode. My hope is this will keep our code consistent and minimize unnecessary diffs in git (for example, changing of quotes, semi-colons or tab spaces)
I also installed a package to organize tailwind classnames in accordance to their documentation and opted to use es6 import modules in the backend to stay consistent with these standards and removed some boilerplate files. I moved the products array into its own constants file to clean up
backend/index.js
so we can have dummy data in that file for testing purposes.Additional info
May need to verify that the eslint and prettier configs are working correctly in your remote workspace