chore(nargo): abstract paths from nargo's working directory #761
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)
Description
Summary of changes
Currently we make assumptions in a number of places that
nargo
is running in the project directory which we want to interact with. This isn't ideal in a CI or workspace contexts as often the noir project of interest will be in a deeper directory compared to wherenargo
is run.I've made the directory relative to which
nargo
should perform its actions (saving circuits, reading inputs, etc.) explicit with thepaths
option. After testing this I have then removed the flag from the CLI so people don't start relying on this (We don't really want people to pass in paths directly rather than having some form of workspace).Dependency additions / changes
N/A
Test additions / changes
N/A
Checklist
cargo fmt
with default settings.Additional context