waalge
/
aiken
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Build LSP projects with verbose tracing level 

Without that, the language server might trigger awkward warnings about
  unused imports due to trace stripping. So it's better to compile/check
  projects in the language server in the most expanded form.
This commit is contained in:
KtorZ 2024-10-01 16:12:41 +02:00
parent 0060804d1a
commit 51b6b77db8
No known key found for this signature in database
GPG Key ID: 33173CB6F77F4277
2 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
CHANGELOG.md
View File

@ -10,6 +10,7 @@
- **aiken-lang**: Fix compiler crash on trace + expect as last expression of a clause. See #1029. @KtorZ - **aiken-lang**: Fix compiler crash on trace + expect as last expression of a clause. See #1029. @KtorZ
- **aiken-lang**: Fix redundant warning on introduced identifiers when destructuring validator params. @KtorZ - **aiken-lang**: Fix redundant warning on introduced identifiers when destructuring validator params. @KtorZ
- **aiken-lsp**: Compile project using verbose tracing, to avoid having the language server complain about unused imports. @KtorZ
- **uplc**: Fix (again :grimacing:) cost-models for PlutusV1 & PlutusV2. @MicroProofs - **uplc**: Fix (again :grimacing:) cost-models for PlutusV1 & PlutusV2. @MicroProofs
### Removed ### Removed

2
crates/aiken-lsp/src/server/lsp_project.rs
View File

@ -36,7 +36,7 @@ impl LspProject {
false, false,
u32::default(), u32::default(),
PropertyTest::DEFAULT_MAX_SUCCESS, PropertyTest::DEFAULT_MAX_SUCCESS,
Tracing::silent(), Tracing::verbose(),
None, None,
); );