-
Notifications
You must be signed in to change notification settings - Fork 772
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
Edit walkSync to return items like what walk emits #310
Comments
Sorry, I just wanted to email @jprichardson to ask for his attention regarding this issue, but I accidentally email him through that PR. Bad mistake by me. Obviously that PR is not at all related to this issue. Please accept my apologies. |
Yes, I like this a lot. However, since we just released 1.0.0, this wouldn't make it until 2.0.0 since it's a breaking change. I'd like to release 2.0.0 in early 2017 when we can drop Node v0.12 support. |
Absolutely. So, I will send you a PR. Then, whenever you have time, you can test it and see if it works the way that it is supposed to. |
It would be great to also have directories included in the list as part of this change. |
This feature should be shipped in Jan 2017. @jprichardson Thoughts on @r-murphy's proposal? |
Gah, I think this is a bug and should be there. Maybe for 1.0 we consider |
Docs say:
I agree it's a bit unexpected though. 👍 for redoing or removing |
For |
Fixed by #312 on the v2 branch. Still needs docs. |
@RyanZim I am preparing the docs to include the enhanced |
@jprichardson & I have decided to remove |
What do you think about editing
walkSync
so that it would be consistent withwalk
? That is,walkSync
also returns an array of items{path:, stats:}
instead of only file paths, consistent with whatwalk
emits as its data?The text was updated successfully, but these errors were encountered: