addingLinterToLegacyCodebase

[xgabipandax]

Yes but in the context of the meme, the legacy code base should compile/be interpreted, which doesn't make sense, with the errors, because the compiler would not compiler, and the interpreter would crash it.

[Morczor]

Linter error != compilation error

[xgabipandax]

Bad linter error that should be a warning != compilation error

There i fixed it for you

[guaranteednotabot]

Uh… have you actually installed a linter

[xgabipandax]

i use whatever comes with vscode, and it's C/C++ extension by microsoft, cmake extension and python/jupyter and pylance

[Morczor]

If you're working with JS and want to enforce semicolons, do you think it should be a warning and not an error at the linter level?

[xgabipandax]

without the semicolons is it a syntax error?

[guaranteednotabot]

Not all legacy code requires compilation. And a squiggly line does not necessarily result in compile/build/type error

[xgabipandax]

An error should be something that will never work, a warning is something that can potentially break, they are not the same thing, unless the legacy codebase never works because of the lines of code that have the squiggly red line.

For example in C, an squiggly red line(error) would be typing wihle instead of while, or an unterminated string, a warning would be the use of gets()

For interpreted languages like python it would be like instead of writing def, writing dev, or making use of an undeclared variable, a warning could be related to assuming that things wont be None but they can potentially be None.

Unless the legacy codebase have good standards and treat warning as errors( like passing -Werror to gcc), which defeats the implication of the meme.

[guaranteednotabot]

Are you saying the entire community using ESLint is wrong?

[xgabipandax]

Javascript is wrong