-
Notifications
You must be signed in to change notification settings - Fork 56
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 code is corrected and saved, previous error/problem is still persistent #195
Comments
Can you post the full output of the Crystal output channel? |
The output tab is blank. |
You need to select "Crystal" from the dropdown at the top right of the panel |
[Crystal] extension loaded 1 | def testing_ext(file : string) [Problems] (epub_reader) $ /usr/bin/crystal build src/epub_reader.cr --no-debug --no-color --no-codegen --error-trace -f json -o /dev/null [Hover] getting context... 1 | def testing_ext(file : string) [Hover] error: undefined [Hover] getting context... 1 | def testing_ext(file : string) [Hover] error: undefined [Hover] getting context... 1 | def testing_ext(file : string) [Hover] error: undefined [Dependencies] epub_reader $ /usr/bin/crystal tool dependencies /home/cynthia/projects/crystal/epub_reader/src/epub_reader.cr -f flat --no-color |
The above is from changing "String" to "string" then back. (saving file in between actions.) |
Thank you. In the meantime for things to work you can disable a lot of the features to just use snippets and syntax highlighting. Check this repo's README for more info |
I've also run into some weird ghosting with Crystal sometimes recently. Does it still happen if you try building from the command line? |
Came here to report the same thing. I had a syntax error in a function definition ( |
@gregawoods If there are other problems in the file or potentially the workspace, the error might not go away until all them are resolved. A few questions to help diagnose:
You can also try deleting the cache for this project ( |
Here's the console output. The actions I took here are: Intentionally introduce a syntax error, hit save, fix the error, hit save again.
Now, I've been playing around with the settings.json. I set both |
Describe the bug
After correcting code to eliminate an error, and saving the fie, the previous problem and flagging of the problem does not go a way.
To Reproduce
Make a simple type error in any code. For example use "string" instead of String. Save the file and see the proper error message and red underlining appear. Now change the code from "string" to "String". Save the file. The error message and red underlining do not go away. Close VScode and re-open it. The error message and underlining finally go away.
Expected behavior
Once error is corrected and file is saved, the red underlining and error messages should go away.
Piece of Code
see screenshot
Screenshots
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: