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

Could most of the commands have a --dry-run option? #111

Open
joneshf opened this issue Jul 11, 2022 · 0 comments
Open

Could most of the commands have a --dry-run option? #111

joneshf opened this issue Jul 11, 2022 · 0 comments

Comments

@joneshf
Copy link
Contributor

joneshf commented Jul 11, 2022

I think it would be pretty useful to have a --dry-run option for most of the commands. I dunno that init or list need one, since they don't affect GitHub. There's two reasons why I think this option would be useful:

  1. As a person using spr, it's not always clear what it's going to do before it does it. It'd be nice to know what the game plan is before it executes it.
  2. As a person developing spr, it's not easy to test the behavior of commands. Most everything sends off actual requests to GitHub or updates the local repo, so writing a test for some changes is next to impossible. If each command wasn't always going to affect the real world, it would be easier to get some amount of confidence (not complete confidence) that the behavior of a command is what is expected.

The first reason is probably more easily understandable than the second. But, I think being able to have a suite of tests that validate a game plan could be really beneficial. Any thoughts on the idea?

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

No branches or pull requests

1 participant