-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
lsp panic on bad field #954
Comments
can you should me the panic message? |
|
This is because The LSP functionality in general does not work if a contract will not compile, or at least that is my understanding. |
This was just an example. The error on compilation is more specific than what was coming through on the LSP. The LSP could say "the problem is here ... ->" rather then "something somewhere is wrong" . |
What Git revision are you using?
aiken v1.0.28-alpha+c9a1519
What operating system are you using, and which version?
nixos
Describe what the problem is?
Transaction { withdraws, .. } = transaction
causes lsp to error
I tripped over some unknown labels in a pattern or function
.What should be the expected behavior?
Lsp doesn't error and instead reports issue. Eg
`withdraw` is not a field of `transaction`
This has been around for a long time. I suspect this is a duplicate issue, but a brief browse didn't find it.
Update: Behavior still present on
The text was updated successfully, but these errors were encountered: