You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{path} gets replaced with all of the event's file paths. This could break things for existing users.
{paths} is a new placeholder that gets replaced with all of the event's file paths. This complicates the API.
Any thoughts on which way might be preferable?
If it's a bug
This might be happening because the code is creating a debounced version of the custom command even if the debounce option is set to zero. And/or there might be a similar problem with the throttling. I think it would be simple enough to avoid using those lodash functions if the relevant options are set to zero.
The text was updated successfully, but these errors were encountered:
sbleon
added a commit
to singlebrook/chokidar-cli
that referenced
this issue
Nov 4, 2019
The custom command currently only gets a single path when multiple files were changed:
I'm not sure if this is a bug or a feature.
If it's a feature
I'd like to see either of these changes:
{path}
gets replaced with all of the event's file paths. This could break things for existing users.{paths}
is a new placeholder that gets replaced with all of the event's file paths. This complicates the API.Any thoughts on which way might be preferable?
If it's a bug
This might be happening because the code is creating a debounced version of the custom command even if the debounce option is set to zero. And/or there might be a similar problem with the throttling. I think it would be simple enough to avoid using those lodash functions if the relevant options are set to zero.
The text was updated successfully, but these errors were encountered: