Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Treat eslint warnings as errors on build #168
Actually, there's a problem here. It appears that react-scripts has its own eslint config, but gts has another eslint config. I'd assume we want to switch over to gts's eslint config -- but react-scripts doesn't let you override the eslint config that it uses.
Probably the best way forward is just not to merge this PR and ignore all the warnings from react-scripts that come when running the app. This is sub-optimal though, since developers will see warnings from react-scripts that aren't actually enforced during development. I'm closing this for now @advayDev1 , but let me know what you think.