Skip to content

Wildcard glob support #178

Open
Open
@ghost

Description

It looks like passing a glob to wildcard was a breaking change in the 4.x release (#175), but it's unclear why it was removed. It's an extremely valuable feature and something I've used across multiple applications. Is it possible to revert that change and keep the functionality, or is there a workaround to keep similar behavior without having to rework directory structures?

For one of the use cases specifically, by using globs, it's possible to keep static assets next to the relevant code they're used with rather than having to maintain a separate assets directory. It's in a similar vein of keeping your tests next to the code versus having a separate tests directory, etc.

It'd be awesome to keep this functionality if there wasn't a strong reason to remove it.

EDIT: I did see that #172 was added, but wasn't sure if that would actually allow the same behavior or if there were differences.

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueGood for newcomerssemver-minorIssue or PR that should land as semver minor

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions