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
The Noir VS Code extension does not currently support proving Noir programs within the extension, which could be useful for Noir development workflows in e.g. in-browser VS Code.
Happy Case
As a Noir developer, I want to:
Type <my_desired_proof_name> in a field in the Noir Sidebar View
Click a "Prove" button in the View (which generates a proof of executing the Noir program with selected inputs named <my_desired_proof_name>)
so I can carry out further actions with the proof either in the View or elsewhere (e.g. verifying; exact actions would be covered in other GitHub Issues).
If there is a name clash of <my_desired_proof_name> with an existing proof previously generated and stored in the local instance, the extension should prompt me with an error and ask me to choose an alternative proof name.
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response
The content you are editing has changed. Please copy your edits and refresh the page.
Problem
The Noir VS Code extension does not currently support proving Noir programs within the extension, which could be useful for Noir development workflows in e.g. in-browser VS Code.
Happy Case
As a Noir developer, I want to:
<my_desired_proof_name>
in a field in the Noir Sidebar View<my_desired_proof_name>
)so I can carry out further actions with the proof either in the View or elsewhere (e.g. verifying; exact actions would be covered in other GitHub Issues).
If there is a name clash of
<my_desired_proof_name>
with an existing proof previously generated and stored in the local instance, the extension should prompt me with an error and ask me to choose an alternative proof name.Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response
Pending
The text was updated successfully, but these errors were encountered: