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 errors not showing in jsx files #1150

Closed
wesleybl opened this issue Mar 23, 2023 · 1 comment · Fixed by #1214
Closed

ESLint errors not showing in jsx files #1150

wesleybl opened this issue Mar 23, 2023 · 1 comment · Fixed by #1214
Assignees
Labels

Comments

@wesleybl
Copy link

wesleybl commented Mar 23, 2023

ESLint errors not showing in jsx files in Eclipse 2023-03. I'm using: master of wildwebdeveloper

Steps to reproduce:

  • Clone: https://github.com/wesleybl/test-eslint
  • Run npm installinside the folder test-eslint
  • Open the test-eslint folder as an Eclipse project.
  • See that no errors are shown in the src/test.jsx file.

At first I thought it might be something to do with #1133. But I think it's something different, since the ESLint server constructor is not even called, when we open a jsx file.

Obs:

With wildwebdeveloper 1.0.1 works.
I have not tested with 1.0.2.
In 1.0.3 we also have the error.

@vrubezhny
Copy link
Contributor

It looks like an upstream issue in vscode-eslint.

There is also a problem occurring with TestTypeScript.testHTMLinTSXFile JUnit test in some latest PRs which looks like also related.

@vrubezhny vrubezhny self-assigned this May 16, 2023
@vrubezhny vrubezhny added the bug label May 16, 2023
vrubezhny added a commit to vrubezhny/wildwebdeveloper that referenced this issue May 17, 2023
@vrubezhny vrubezhny linked a pull request May 17, 2023 that will close this issue
vrubezhny added a commit to vrubezhny/wildwebdeveloper that referenced this issue May 17, 2023
vrubezhny added a commit to vrubezhny/wildwebdeveloper that referenced this issue May 17, 2023
vrubezhny added a commit to vrubezhny/wildwebdeveloper that referenced this issue May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants