Skip to content
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

chore(nargo): abstract paths from nargo's working directory #761

Merged
merged 6 commits into from
Feb 11, 2023

Conversation

TomAFrench
Copy link
Member

@TomAFrench TomAFrench commented Feb 7, 2023

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 where nargo is run.

I've made the directory relative to which nargo should perform its actions (saving circuits, reading inputs, etc.) explicit with the paths 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

  • I have tested the changes locally.
  • I have formatted the changes with Prettier and/or cargo fmt with default settings.
  • I have linked this PR to the issue(s) that it resolves.
  • I have reviewed the changes on GitHub, line by line.
  • I have ensured all changes are covered in the description.
  • This PR requires documentation updates when merged.

Additional context

crates/nargo/src/cli/mod.rs Show resolved Hide resolved
crates/nargo/src/cli/test_cmd.rs Outdated Show resolved Hide resolved
auto-merge was automatically disabled February 10, 2023 20:38

Merge queue setting changed

@kevaundray kevaundray added this pull request to the merge queue Feb 11, 2023
Merged via the queue into master with commit 79d34fc Feb 11, 2023
@kevaundray kevaundray deleted the nargo-path-argument branch February 11, 2023 15:28
TomAFrench added a commit that referenced this pull request Feb 14, 2023
* master: (28 commits)
  chore(ci): Add release token to enable runs against release PR (#840)
  feat(ssa): array sort (#754)
  chore: update readme (#811)
  chore: fix clippy (#825)
  chore: remove stale comment on HirFunction.unchecked_from_expr (#827)
  chore: Getter naming refactor (#803)
  chore: updated "HirFunction::unsafe_from_expr" to "HirFunction::unchecked_from_expr" (#823)
  chore: Forbid unsafe code (#824)
  chore: Follow rust naming convention (#801)
  feat(ci): Add concurrency group for rust workflow (#806)
  chore(ssa): rename impl method to follow Rust guideline (#782)
  fix(nargo): `nargo test` now only runs test functions defined in the current module (#805)
  chore(nargo): Remove outdated error message when Prover/Verifier.toml is missing (#807)
  chore(ssa): rename codegen to ssa_gen + reorg of `Value` struct (#797)
  chore(nargo): abstract paths from nargo's working directory (#761)
  chore(ci): Rename workflows (#804)
  feat: Impls with generics (#798)
  chore(ssa): Add doc comments on `Opcode` struct (#778)
  fix: operators issuing type errors when used with matching integer types arising from generic code (#789)
  chore(nargo)!: bump MSRV to 1.66.0 (#799)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants