fix(nargo): restore nargo codegen-verifier
functionality
#1185
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issue(s)
Resolves #
Description
Summary of changes
Looks like we got a bit ahead of ourselves and started using
eth_contract_from_vk
against a commit ofaztec_backend
where that isn't implemented yet. If you runnargo codegen-verifier
on v0.4.0 you getThis PR reverts to
eth_contract_from_cs
and adds an integration test that if you runcodegen-verifier
the command succeeds and you get some file created.I haven't made any change to
nargo::ops::codegen_verifier
as that's backend agnostic and I don't want to make a breaking change to fix this.Dependency additions / changes
Test additions / changes
Checklist
cargo fmt
with default settings.Documentation needs
Additional context