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

Improve env building (not always automatic). #32

Open
kariharju opened this issue Jun 14, 2024 · 2 comments
Open

Improve env building (not always automatic). #32

kariharju opened this issue Jun 14, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@kariharju
Copy link
Contributor

Issue by fabioz
Wednesday May 31, 2023 at 11:28 GMT
Originally opened as robocorp/robotframework-lsp#934


Do you think it makes more sense to not build an env automatically until you decide to run the bot?

Just in a run may be a bit hard (because until changes are applied you won't have code-completion for the changed libraries and could have errors in code analysis due to that).

I think it could be something as manual command to rebuild + rebuild on run or maybe something as a pop-up when a change is detected and then the user can click that to do the rebuild.

@kariharju kariharju added enhancement New feature or request robocorp-code labels Jun 14, 2024
@kariharju
Copy link
Contributor Author

Comment by fabioz
Tuesday Apr 02, 2024 at 10:25 GMT


Note: this same issue is being used for the use case of forcing a build at a given time without waiting for the automatic build to kick in.

@ottonautti
Copy link

Having control over triggering environment builds would be most useful indeed. Current behavior feels way too eager. It practically prevents using the extension in projects where venv needs to be built manually (using rcc venv).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants