-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Change project description #37
Comments
Reading this portion of the bach docs help me understand:
Sounds very cool... |
This uses the standard gulpjs org readme template. This project has too many applications to be shoehorned into "use in this scenario". Bach is just one application of this and many npm packages use it in their own way. |
I'm not suggesting changing the template @phated, just saying that the current tagline isn't very descriptive. Perhaps it should be something more like: Allows libraries to handle various caller provided asynchronous functions uniformly. Maps promises, observables, child processes and streams, and callbacks to callback style. |
I'd be open to changing the project description. Please send a PR to further discuss. I've changed the title and reopened this. |
As I understand it, this is some sort of converter between async model conventions, but I'm unclear when I'd use it. I suggest a small scenario section at the top of the README might help clarify.
The text was updated successfully, but these errors were encountered: