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
There is no way to exclude only one of them from being iterated upon, because both of them are tested as README.md.
Similarly for folders:
src/utils/
spec/utils/
There is no way to only hit one of these.
The only alternative I can see is to do many calls to node-dir on deeper starting paths so that I can specify more specific rules per call - but that doesn't scale well as directories get deeper and is not refactor-friendly if directories get moved around. This could be easily solved if there were some way to pass the full path to matches.
The text was updated successfully, but these errors were encountered:
Suppose I have the following files:
There is no way to exclude only one of them from being iterated upon, because both of them are tested as
README.md
.Similarly for folders:
There is no way to only hit one of these.
The only alternative I can see is to do many calls to
node-dir
on deeper starting paths so that I can specify more specific rules per call - but that doesn't scale well as directories get deeper and is not refactor-friendly if directories get moved around. This could be easily solved if there were some way to pass the full path tomatches
.The text was updated successfully, but these errors were encountered: