Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Eslint reports no error #3206

Closed
provokateurin opened this issue Sep 11, 2024 · 1 comment · Fixed by #3207
Closed

Eslint reports no error #3206

provokateurin opened this issue Sep 11, 2024 · 1 comment · Fixed by #3207
Assignees
Labels
3. to review Items that need to be reviewed bug

Comments

@provokateurin
Copy link
Member

How to use GitHub

  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Steps to reproduce

  1. npm run lint

Expected behaviour

It should show errors like those displayed in IntelliJ.

Actual behaviour

No errors are reported and the exit code is 0.

@provokateurin provokateurin added bug 1. to develop Issues that are ready for development labels Sep 11, 2024
@provokateurin provokateurin self-assigned this Sep 11, 2024
@provokateurin
Copy link
Member Author

Ah it only happens because .ts(x) files are not checked :/

@provokateurin provokateurin added 3. to review Items that need to be reviewed and removed 1. to develop Issues that are ready for development labels Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Items that need to be reviewed bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant