julius-retzer
commented
2 years ago - Added auto eslint config (fixed the issue when it didn't work in VS Code)
- Add next js eslint config
- Added tailwind CSS rules (it catches some classes that are actually not tailwind classes, quite useful. It also reorders the classes to be consistent)
- Made all errors only warnings, since it would fail the build. This way it will be easier to gradually fix the errors
- Autofixed errors
- Turned off / configured some rules that I don't think are relevant/useful for our situation
- I suggest you go through the config and the errors and adjust the config according to your needs