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
Currently, soldeer assumes that the dependencies dir, the lock file, the foundry config file, the soldeer config file and the remappings file are localed in the current working directory. We could allow for more flexibility (running soldeer commands from a sub-directory) by traversing the file tree upwards until we find a foundry project root (a folder that contains a foundry.toml or soldeer.toml file), instead of using env::current_dir().
The text was updated successfully, but these errors were encountered:
It's not a great UX if a user has to pass an additional arg if they want to run soldeer install package~version from the src or test directory (that's an example).
Currently, soldeer assumes that the dependencies dir, the lock file, the foundry config file, the soldeer config file and the remappings file are localed in the current working directory. We could allow for more flexibility (running soldeer commands from a sub-directory) by traversing the file tree upwards until we find a foundry project root (a folder that contains a
foundry.toml
orsoldeer.toml
file), instead of usingenv::current_dir()
.The text was updated successfully, but these errors were encountered: