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
I am unable to "Goto Type Definition..." or "Goto Definition..." on eslint-plugin-perfectionist. It works for @eslint/js, globals, and typescript-eslint in eslint.config.mjs.
I originally found this issue in a new Angular project and opened this ticket with the plugin developers. They have been very helpful in looking into this issue, but believe it is outside of their code. I created the above brand new repo to try and replicate the bug. But I was not able to get the same error message. However the code discovery actions are not working so it feel like there is something here to diagnose. But I am uncertain how to proceed.
When I reported this issue to LSP-typescript I was told:
To be clear, Vtsls and VS Code do have the correct behavior, I just don't know what causes that behavior. typescript-language-server is just a thin abstraction on top of tsserver.
I wonder what is the difference is between eslint-plugin-perfectionist and @eslint/js, globals, and typescript-eslint? Because those all Goto Definition for me.
Uh oh!
There was an error while loading. Please reload this page.
I am unable to "Goto Type Definition..." or "Goto Definition..." on
eslint-plugin-perfectionist
. It works for@eslint/js
,globals
, andtypescript-eslint
ineslint.config.mjs
.Minimal reproduction repo: https://github.com/rgant/tmp-eslint-perfectionist-test
I originally found this issue in a new Angular project and opened this ticket with the plugin developers. They have been very helpful in looking into this issue, but believe it is outside of their code. I created the above brand new repo to try and replicate the bug. But I was not able to get the same error message. However the code discovery actions are not working so it feel like there is something here to diagnose. But I am uncertain how to proceed.
When I reported this issue to
LSP-typescript
I was told:The text was updated successfully, but these errors were encountered: