-
Currently, the popover remains loaded after clicking on "Go to definition" when the definition location is behind the popover
![CleanShot 2022-09-19 at 13 34 45](https://user-images.githubuserconte…
-
@Kha suggested exploring how *go to definition* could look like for a type shown in a hover. It seems the front end part of this feature would work quite well, with a few drawbacks.
1. Markdown cod…
-
I see that "Go to definition" works for used commands, but not for the the use statement.
For example:
```
use ../hello.nu hello
def main [] {
hello
}
```
Go to definition works on t…
-
When importing like this
```
import "@openzeppelin/contracts/utils/Strings.sol";
```
I cannot Go To Definition.
However if I import like this:
```
import "../node_modules/@openzeppelin/contra…
-
I've noticed that there are scenarios where F12 will take me to the definition for a variable definition, file, etc. where the touchbar "Go to definition" button does nothing. Is this the intended beh…
-
**Describe the bug**
Go to definition (F12) is available from the Editor context menu but the very same option is disabled in the Go menu.
**To Reproduce**
Click on the Go menu. The option is gra…
-
### Issue Report Checklist
* [x] Searched the [issues page](https://github.com/spyder-ide/spyder/issues?q=is%3Aissue) for similar reports
* [x] Read the relevant sections of the [Spyder Troublesho…
-
Feature: Go To Definition should support function definitions as well as fully resolve Definitions
Current Situation: Function definitions not supported, For supported symbols Go To Definition …
-
Issue Type: Bug
F12 does not always work or takes forever.
I've tried the jedi flag, still no change. The problem seems to disappear if VS Code is restarted. After some hours it comes back. Some …
-
See the screenshot below.
When attempting to use the go to definition on a variable it doesn't seem to work.
The .vstags file was generated, but it doesn't seem to have anything useful (attached…