-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
isBinaryFileSync + isBinaryFile #11
Comments
I think the README is just totally wrong. The |
Thanks :-) The thing is, considering the It is just a sugar but 1) the code gets more readable 2) smaller number of lines of code in the function and 3) easier to test. |
👍 That is too magic. What I usually do is export the async function on |
I'm going to implement a separate Sync method now, since there is interest. |
Reading the README, it is very strange to have
isBinaryFileSync
being async just because the second argument is a function.Having the distinct functions would at least match Node.js sync/async declarations.
In any case, having a *Sync async function is just bad in term of naming.
The text was updated successfully, but these errors were encountered: