Developers often have the workflow - when they encounter an error, they copy it, and then paste it (either into google, github repo or org search, or as a global search in the IDE library (if they're internal devs)).
Breaking up long error messages into multiple lines prevents this workflow (the global search in the code comes up empty, which is a frustrating experience).
I propose we add an exception to the max-len line, specifically for error message literal strings (but not backticks).
(Or informally approve the usage of eslint-disable-next-line max-len in those contexts.)
Developers often have the workflow - when they encounter an error, they copy it, and then paste it (either into google, github repo or org search, or as a global search in the IDE library (if they're internal devs)).
Breaking up long error messages into multiple lines prevents this workflow (the global search in the code comes up empty, which is a frustrating experience).
I propose we add an exception to the max-len line, specifically for error message literal strings (but not backticks). (Or informally approve the usage of
eslint-disable-next-line max-lenin those contexts.)