You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create common configurations that can be reused between all repositories. Currently each repository defines it's own configurations for stuff like eslint, TypeScript, etc. This can lead to inconsistent development experiences between projects. If a project needs something specific, they should either modify the common one or create it from scratch. But sets of common configurations should also be available.
We should add configurations for at least the following tools:
However I am open to more, if they are useful. Some examples may be:
.prettierrchttps://prettier.io. This can be maybe useful? I dislike prettier simply because I prefer eslint to actually show errors, rather than hide them. It's also a very opinionated tool with little room to configure, and some of its defaults break our eslint config
.vscode/settings.json. This would only really be useful for VS Code users however
Replacing our existing config parser in our TypeScript projects with some thing like https://neatojs.com/docs/config? Though I'm not sure. That config tool is nice but I'm not sure if the use of double underscores would be intuitive or not, and I'm not sure how we can handle cases where a setting is optional and has a default value? Going to ping @mrjvs for input since he made this
The text was updated successfully, but these errors were encountered:
Create common configurations that can be reused between all repositories. Currently each repository defines it's own configurations for stuff like eslint, TypeScript, etc. This can lead to inconsistent development experiences between projects. If a project needs something specific, they should either modify the common one or create it from scratch. But sets of common configurations should also be available.
We should add configurations for at least the following tools:
.editorconfig
https://editorconfig.org. All projectseslint.config.js
https://eslint.org. Setup to use TypeScript. Only useful for TypeScript projectstsconfig.json
https://www.typescriptlang.org/tsconfig. Only useful for TypeScript projects.golangci.yml
https://golangci-lint.run. Only useful for Go projectsHowever I am open to more, if they are useful. Some examples may be:
.prettierrc
https://prettier.io. This can be maybe useful? I dislike prettier simply because I prefer eslint to actually show errors, rather than hide them. It's also a very opinionated tool with little room to configure, and some of its defaults break our eslint config.vscode/settings.json
. This would only really be useful for VS Code users howeverThe text was updated successfully, but these errors were encountered: