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
To prevent dependency-cycles multiple commands currently by default remove dev-dependencies from the Cargo.toml-files first. While neat, the UX is still lacking because:
if you change specific files an then run the command, you can't just commit what you had before, because the files were edited
if the command fails, you have to revert all chagnes and do your local changes again, as it is pretty hard to figure out what had changed
Let's do the following:
create a .Cargo.toml.backup when we remove the dev-deps
only create that file when we actually removed dev-deps
add another command to quickly revert-de-dev-dep copying back the backup files. allowing to jump back to the state before
maybe automatically run that revert if the patching-command failed?
The text was updated successfully, but these errors were encountered:
To prevent dependency-cycles multiple commands currently by default remove dev-dependencies from the
Cargo.toml
-files first. While neat, the UX is still lacking because:Let's do the following:
.Cargo.toml.backup
when we remove the dev-depsrevert-de-dev-dep
copying back the backup files. allowing to jump back to the state beforeThe text was updated successfully, but these errors were encountered: