-
-
Notifications
You must be signed in to change notification settings - Fork 273
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
After opening diff editor, analysis temporary goes wrong #1810
Comments
That's a good guess - I think we'd need to make sure in FsAutoComplete that git-schemed URIs are just entirely ignored for open/close/etc notifications |
ionide/FsAutoComplete#1031 FSAC issue |
I'm having a similar issue as well. Any time I open the a file from the "Source Control" panel for comparison, the original version is picked up for compilation instead of the current version. |
As a workaround for noq, you should be able to save the file and type checking should come back. |
Resolved at v7.4.1. Thank you! |
Thank you for fixing this! I saw the GitHub release, but it's not available in the Marketplace yet. |
I also can't find this release in the Marketplace. Will installing it manually affect future auto updates? |
We're having an issue with the release pipeline that we're digging into, but it is perfectly safe to install from the vsix on the GitHub release - VSCode will seamlessly pick up future updates. |
|
Describe the bug
When I open a diff editor of F# file and go back to a text editor, analysis (diagnostics, hover, rename) doesn't work, until I input in text editor.
Steps to reproduce
Program.fs
) is committed to git repositoryProgram.fs
in a text editor tabProgram.fs
in itProgram.fs
will be opened. Close itProgram.fs
, hover doesn't work correctlyLink to sample reproduction
Expected behaviour
Analysis work as usual
Screenshots
peek-ionide-issue.mp4
Machine info
Additional context
In trace, VSCode sent a didOpen message with
git:
scheme URI to server:and didClose later:
I guess, that didOpen message has written contents of text document in server cache, perhaps due to ignoring scheme.
The text was updated successfully, but these errors were encountered: