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

Update readme #25

Open
markijbema opened this issue Dec 12, 2013 · 10 comments
Open

Update readme #25

markijbema opened this issue Dec 12, 2013 · 10 comments
Labels

Comments

@markijbema
Copy link
Contributor

I was browsing around the code and am amazed at the amount of functionality which I didn't see from the readme. I think it would be really worthwhile to update the readme with the functionality at least, even if it isn't very well written/with lots of examples for now. I really think this is a great gem, and it apparantly is even better than I thought :)

@kytrinyx
Copy link
Contributor

I think you're right that the README could use more examples.

Could some of the test-cases be a basis for the examples?

@markijbema
Copy link
Contributor Author

Yes, I think that would work pretty well :) Also the CLI should be documented (I was totally surprised that that existed ;) ).

@kytrinyx
Copy link
Contributor

Yes, good call!

@markijbema
Copy link
Contributor Author

Wondered about this today, but any reason for not following -i/-f semantics? I'd say -i should do -ask true, -f should do -ask false, and the default is up to you.

@kytrinyx
Copy link
Contributor

Is that --interactive and --force? How is --force the same as "don't ask, do nothing"?

@markijbema
Copy link
Contributor Author

Ah sorry, I didn't read the updated readme yet. You're right of course. In that case --force is the option I'm missing ;)

@markijbema
Copy link
Contributor Author

Actually, now I think about it, 'verify --ask false' is a strange name for 'diff'. When you call verify with ask I'd say you're not really verifying. What about

  • approvals diff == approvals verify --ask false
  • approvals verify == approvals verify --ask true
  • approvals verify -f == echo -e "y\ny\ny\n" | approvals verify --ask true

I might be missing something though, because I only use the default verifyer, and not the vimdiff, but I expect this would work the same in that case right?

(on a sidenote, any reason you use -a in your vim-mapping? That's the default, right?)

@kytrinyx
Copy link
Contributor

Actually, now I think about it, 'verify --ask false' is a strange name for 'diff'.

Yeah that's fair, but I don't like the syntax:

$ approvals diff --diff vimdiff

I agree that if we have an approvals diff that never asks, it makes sense to have approvals verify that always asks.

As for the third suggestion, I can imagine a use case where you would want to automatically accept the new output.

(on a sidenote, any reason you use -a in your vim-mapping? That's the default, right?)

I think what I originally intended was a flag that is true if present, false if absent. Looking at it again, I totally screwed that up.

@markijbema
Copy link
Contributor Author

approvals view?

@kytrinyx
Copy link
Contributor

Oooh, I like that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants