You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clarinet requirements should be downloaded in the .cache directory so that the LSP can check for errors the project.
A few things can trigger the download of the requirements, such as clarinet check or console.
Opening a clarinet project in VSCode (with the extension) should also automatically download it.
Bug
The extension doen't download the requirements and instead silently fails.
It used to work in the past
Solution
Bring back requirements deployment on project opening
The text was updated successfully, but these errors were encountered:
Context
Clarinet requirements should be downloaded in the .cache directory so that the LSP can check for errors the project.
A few things can trigger the download of the requirements, such as clarinet
check
orconsole
.Opening a clarinet project in VSCode (with the extension) should also automatically download it.
Bug
The extension doen't download the requirements and instead silently fails.
It used to work in the past
Solution
Bring back requirements deployment on project opening
The text was updated successfully, but these errors were encountered: