You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it turns out, line endings are still problematic when using different OS (Windows / Linux). The usage of eslint should minimize the problem, but if the linter is run on the command line there are still problems (see comment #458 (comment)).
In VSCode, one thing a developer can do is to use the eslint-prettier plugin. This info should be part of the documentation.
It would also be nice to know why running eslint on the command line does not work as expected, while using the VSCode plugin works.
The text was updated successfully, but these errors were encountered:
As it turns out, line endings are still problematic when using different OS (Windows / Linux). The usage of eslint should minimize the problem, but if the linter is run on the command line there are still problems (see comment #458 (comment)).
In VSCode, one thing a developer can do is to use the eslint-prettier plugin. This info should be part of the documentation.
It would also be nice to know why running eslint on the command line does not work as expected, while using the VSCode plugin works.
The text was updated successfully, but these errors were encountered: