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
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.
The text was updated successfully, but these errors were encountered:
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).
Issue by fabioz
Wednesday May 31, 2023 at 11:28 GMT
Originally opened as robocorp/robotframework-lsp#934
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.
The text was updated successfully, but these errors were encountered: