Skip to content

Add option to test patterns on full path instead of base name #49

@Mr-Wallet

Description

@Mr-Wallet

Suppose I have the following files:

src/README.md
spec/README.md

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions