Document how one can obtain and install this extension

[ittaiz]

Hi,
I'd really like to use this :)
From the readme it's not clear how one should do this. I tried cloning the repo, building it with npm but then got stuck on installing vsce which I read is how I'm supposed to install manually built extensions.
If I'm on the right path I think documenting it will be super helpful. If I'm not then even more :)

Thanks for all your work...

[allevato]

Now that the debugger is in place and the extension has reached the point of being somewhat useful, I plan to spend some time over the next few days setting everything up to get it in the extension marketplace.

[ittaiz]

Awesome! I’ll wait. Riddled with the above because I wanted to show it off to my colleagues. We’re all looking forward to it...

…

On Sun, 11 Nov 2018 at 21:58 Tony Allevato ***@***.***> wrote: Now that the debugger is in place and the extension has reached the point of being somewhat useful, I plan to spend some time over the next few days setting everything up to get it in the extension marketplace. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#10 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABUIFx0BEBrUmwRPEJNWFfQGR7H7MOm-ks5uuIFIgaJpZM4YYn-N> .

[laurentlb]

I have no experience with VS Code, but I wanted to try it.

$ git clone https://github.com/bazelbuild/vscode-bazel.git
$ cd vscode-bazel
$ npm install
$ code

• File > Open Folder > select the vscode-bazel directory
• Ctrl-F5 - this opens another VS Code window
• Open a directory with your Bazel project.
• If everything goes well, you should see the list of targets under "Bazel Build Targets"
• I've set breakpoint in my bzl file, but I didn't manage to get Bazel to break.

Here's the log:

INFO: Debugger connection successfully established.
Loading: 
Loading: 0 packages loaded
Analyzing: target //:aa (1 packages loaded, 0 targets configured)
DEBUG: /usr/local/google/home/laurentlb/tmp/bazel/a.bzl:2:3: hello
DEBUG: /usr/local/google/home/laurentlb/tmp/bazel/a.bzl:3:3: <rule context for //:aa>
INFO: Analysed target //:aa (1 packages loaded, 1 target configured).
INFO: Found 1 target...
[0 / 1] [-----] BazelWorkspaceStatusAction stable-status.txt
Target //:aa up-to-date (nothing to build)
INFO: Elapsed time: 1.106s, Critical Path: 0.01s, Remote (0.00% of the time): [queue: 0.00%, setup: 0.00%, process: 0.00%]
INFO: 0 processes.
INFO: Build completed successfully, 1 total action
INFO: Build completed successfully, 1 total action
INFO: Debug server listener thread closed; shutting down debug server and resuming all threads
INFO: Debug server listener thread closed; shutting down debug server and resuming all threads

So I know that the debugger was connected, I know that my code was evaluated (I've put breakpoints on the print lines`), but it didn't stop.

[allevato]

The logic to map local file paths to the file paths that Bazel sees internally when evaluating breakpoints is a little hairy. Could this be failing for you?

[laurentlb]

Yes.
The variable sourcePathInExternal points to something that doesn't exist.

I got it to occasionally work using:
const sourcePathInExternal = path.join(this.bazelInfo.get("workspace"), relativeSourcePath);
but it's not reliable

[ittaiz]

Any update on this? Don't mean to badger but I'm super psyched about this :)

[allevato]

I've set up the marketplace but it looks like the release has an issue that wasn't present during development (#14). Since it's available now I'll close this specific issue, but keep an eye on that one for a resolution.

[ittaiz]

btw, it might be obvious to most people but I'd still add a sentence in the readme on how to obtain this extension