Skip to content

dev experience: cargo dev remove + cargo dev setup ... --remove #8663

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

Closed
yoav-lavi opened this issue Apr 8, 2022 · 0 comments · Fixed by #8664
Closed

dev experience: cargo dev remove + cargo dev setup ... --remove #8663

yoav-lavi opened this issue Apr 8, 2022 · 0 comments · Fixed by #8664

Comments

@yoav-lavi
Copy link
Contributor

yoav-lavi commented Apr 8, 2022

Description

I think that having (in addition to the existing command) a remove flag / alias under setup (e.g. cargo dev setup intellij ..., cargo dev setup intellij --remove) might be good for visibility.

If it's been a while since you've setup the editor and now need to remove to commit, you're more likely to remember what you did or press up multiple times than remember the feedback info when running the command.

It also makes sense to me as setup and intellij are subcommands which you want to perform an additional operation on when removing the setup.

I've personally ended up rolling back the files manually since I didn't remember the additional command, so this would have been helpful.

Would be willing to open a PR for this if it's agreed upon!

(of course if there's a way to keep the setup permanent locally with a separate file and a .gitignore, that would be even better)

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 a pull request may close this issue.

1 participant