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
It would be best if we could generate a build task in the normal flow of vscode instead of a build command.
This allows you to add flags and configure the actual command to your liking.
The text was updated successfully, but these errors were encountered:
I already thought about that idea too. Maybe we can use both in parallel? It would also avoid to query targets all the time you want to build one specific target. Maybe we can introduce a new command like 'configure build tasks'.
I also thinks that a good idea. In my mind I was more thinking to implement the auto task detection, like for npm. I try to do so and finally manage to a result (I follow this sample). Also to avoid query each time bazel I do like them, and cache the result, note that it become invalid if a bazel file is modified.
@ErikBehar For the configuration part that you mention, my current solution do not solve it, because I do not get the Tasks definitions when I have to create them... It a little be strange but I think that direcly link to this issue. I may write a workaround in the futur (but hope that Microsoft solve the issue quickly)
How to test the version:
git clone https://github.com/quentingodeau/vscode-bazel-tools.git
cd vscode-bazel-tools
git checkout feature/task-provider
npm install
npm run compile
Then open vscode and open the vscode-bazel-tools folder
Finally press F5
It would be best if we could generate a build task in the normal flow of vscode instead of a build command.
This allows you to add flags and configure the actual command to your liking.
The text was updated successfully, but these errors were encountered: