It's annoying that each sub-project has to repeat a bunch of style rules (ex. the prettier configuration, or the import/order rule), when they should be defined for everything inside the git repo. The problem is, each subdirectory might have its own extensions (ex. react for the client, and nodejs stuff for the server).
Ideally, we want:
[ ] A .tsconfig.json, .eslintrc.js and .eslintignore, .stylelintrc.js and .stylelintignore on the parent directory
[ ] The same files defined in each sub-directory, but only for the extra plugins, rules, and config options that apply to that type of project
[ ] The package.json script for lint shouldn't have to cd into each subdirectory
[ ] The parent project shouldn't have to install dependencies to run lint rules in each subdirectory, but it's not a big deal if it has to
It's annoying that each sub-project has to repeat a bunch of style rules (ex. the
prettierconfiguration, or theimport/orderrule), when they should be defined for everything inside the git repo. The problem is, each subdirectory might have its own extensions (ex.reactfor the client, andnodejsstuff for the server).Ideally, we want:
.tsconfig.json,.eslintrc.jsand.eslintignore,.stylelintrc.jsand.stylelintignoreon the parent directorypackage.jsonscript forlintshouldn't have tocdinto each subdirectoryHere's a Stackoverflow post to use as a jumping off point: https://stackoverflow.com/questions/33618741/how-to-handle-a-project-with-multiple-tsconfig-json-files/41860128#41860128