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

fix: find nargo in path if nargoPath is blank #99

Merged
merged 1 commit into from
Feb 4, 2025

Conversation

asterite
Copy link
Contributor

@asterite asterite commented Feb 3, 2025

Description

Problem

Resolves an issue where if nargoPath was empty it wouldn't pick up nargo in PATH.

Summary

Additional Context

I don't know how it used to work. Maybe by default it starts in undefined, but then if you change it and erase it it ends up being an empty string.

PR Checklist

  • I have tested the changes locally.
  • I have formatted the changes with Prettier and/or cargo fmt on default settings.

@asterite asterite requested a review from a team February 3, 2025 15:43
@TomAFrench
Copy link
Member

Is this potentially caused by #91?

@asterite
Copy link
Contributor Author

asterite commented Feb 3, 2025

Ah, it seems so. Previously it was doing config || ... and apparently "" || "something" is "something" in JS.

@asterite asterite merged commit 73b684a into master Feb 4, 2025
4 checks passed
@asterite asterite deleted the ab/check-nargo-path-is-undefined-or-empty branch February 4, 2025 10:51
@github-actions github-actions bot mentioned this pull request Feb 4, 2025
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