lsp panic on bad field

[waalge]

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.

[rvcas]

can you should me the panic message?

[waalge]

 Error 02:24:24 PM lsp.message LSP Message (aiken) I tripped over some unknown labels in a pattern or function.

[Riley-Kilgore]

This is because withdraws is not a field of transaction and you should use the label withdrawals instead.

https://github.com/aiken-lang/stdlib/blob/d8f3e57bf0688dfc5e5ce9a8819109ef67e7da62/lib/aiken/transaction.ak#L62

The LSP functionality in general does not work if a contract will not compile, or at least that is my understanding.

[waalge]

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" .