Skip to content
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

The VSCode extension does not download requirements when opening a project #1656

Open
Tracked by #1672
hugocaillard opened this issue Feb 4, 2025 · 0 comments
Open
Tracked by #1672
Labels
bug Something isn't working

Comments

@hugocaillard
Copy link
Collaborator

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

@github-project-automation github-project-automation bot moved this to 🆕 New in DevTools Feb 4, 2025
@hugocaillard hugocaillard moved this from 🆕 New to 📋 Backlog in DevTools Feb 6, 2025
@hugocaillard hugocaillard added the bug Something isn't working label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant