Open 64J0 opened 7 months ago
Some languages like TypeScript are able to provide a choice when there are several candidates:
I wonder if we should do something similar, it could also make it easier to navigate between signature and implementation files in general.
Yeah - we have several gaps in navigation/references/etc with regards to separating implementation, declaration, and definition. A lot of this should come down to locating and returning different locations for
but we'd need to do that and see how far that gets us in covering the UX gaps.
I started some of that work in https://github.com/fsharp/FsAutoComplete/pull/1111
Describe the bug
In VSCode, when I have both the signature and implementation files for the same functions and I want to go for the function implementation, it redirects me to the signature instead. It would be very nice if this behavior could be customized to redirect to the implementation instead (maybe some switch on the extension configurations).
Steps to reproduce
.fsi
) and implementation (.fs
) files for some function;Link to sample reproduction
Expected behaviour
Redirect to the implementation instead of the signature.
If you're going to keep the redirect to the signature by default, it would be nice to have some configuration in the extension settings to allow it to redirect to the implementation instead of signature.
Screenshots
Machine info
Additional context
Add any other context about the problem here.