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.

Sign up for GitHub

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

Jump to bottom

ESLint extension broken on VSCode Insider release #1334

Closed
dbaeumer opened this issue Sep 9, 2021 · 0 comments
Closed

ESLint extension broken on VSCode Insider release #1334

dbaeumer opened this issue Sep 9, 2021 · 0 comments
Labels
bug Issue identified by VS Code Team member as probable bug
Milestone
2.1.25

Comments

@dbaeumer
Copy link
Member

dbaeumer commented Sep 9, 2021

The reason is the change of the proposed Window.openEditors API in VS Code which we use in LSP for pull model diagnostics

Since ESLint is not depending on this we can disable the proposed features for now.
@dbaeumer dbaeumer added this to the 2.1.24 milestone Sep 9, 2021
@dbaeumer dbaeumer added the bug Issue identified by VS Code Team member as probable bug label Sep 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Milestone
2.1.25
Development

No branches or pull requests
1 participant
@dbaeumer