-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat: Add execute command to handle Execute code lens #31
Conversation
78fe2a9
to
8e22cd7
Compare
I'm building this with Should I be doing something different to test this? |
So the published extension doesn't work for you either? I use a custom absolute path to my nargo binary since I iterate on the features so I've not experienced this. Seems entirely unrelated to this PR |
Yeah, I really doubt it has anything to do with this PR. Just trying to get to a state where I can meaningfully test it. |
I'm guessing that your vscode shell doesn't have access to a nargo in its path. I'm going to see if I can replicate but you can also add a hardcoded path in settings. |
I don't get any errors on the published extension (v0.0.3) but nothing past syntax highlighting either. I've switched back to the locally installed extension and don't get the error anymore but no output either. Adding an explicit path causes no change. |
Ah ha! I've managed to get signs of life. |
Ok, I can execute circuits using this now. |
Description
Problem*
Ref noir-lang/noir#2330
Summary*
This adds a
nargo.execute
command that will be triggered via the> Execute
code lens.Additional Context
PR Checklist*
cargo fmt
on default settings.