Meanwhile in another universe one of my biggest win was to introduce this line in our PR validation pipeline.
eslint . --max-warnings 0
Meanwhile in another universe one of my biggest win was to introduce this line in our PR validation pipeline.
eslint . --max-warnings 0
This may work if the developer is a possible client too like in this case. But I feel that’s the exception.
Do what the clients want and not what developers, designers or management want.
In a codebase with a lot of warnings is even better for me to add a disable comments for all the existing warning and then not allow any new one in.
And then each time a part of the code needs to be touched the existing warning there should be solved too.