-
-
Notifications
You must be signed in to change notification settings - Fork 586
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
Implement ready event. Fixes #102 #103
Conversation
Seems like that complicates chokidar A LOT. Does your current solution work fine for you? |
Nope, it's very flaky, can't find a correct delay time that always works. I wonder if there is a cleaner way to do this On Monday, February 24, 2014, Paul Miller notifications@github.com wrote:
|
Of course.
|
I'm not sure I understand how will this work. But are you open to adding On Monday, February 24, 2014, Paul Miller notifications@github.com wrote:
|
yes, the solution I mentioned is a lot simpler and has no perf impact so I will be glad to merge it |
cool, now to try to understand your solution.
I must be missing something |
hmm you're right. OK in this case I suggest you to try out your fork in production. Maybe after some time and tests you will see it's stable and we can think of something then. (not comfortable with merging this big change without any production tests) |
alright, thanks man |
( |
A ready event for every
.add
call seems appropriate to notify the user that we're ready to detect file changes.