Please check if the PR fulfills these requirements
[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature.
What is the current behavior? (You can also link to an open issue here)
The current file detection Regexp is very strict and doesn't allow using of wildcards as part of the filename while the Symfony Finder component allows it - https://symfony.com/doc/current/components/finder.html#file-name (and even Regexp).
What is the new behavior (if this is a feature change)?
I'm not sure we really need to validate file extensions for our purposes. So the simplified Regexp allows using anything as the file name. It brings benefits for *.js* matching both js and jsx files for instance.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) Feature.
What is the current behavior? (You can also link to an open issue here) The current file detection Regexp is very strict and doesn't allow using of wildcards as part of the filename while the Symfony Finder component allows it - https://symfony.com/doc/current/components/finder.html#file-name (and even Regexp).
What is the new behavior (if this is a feature change)? I'm not sure we really need to validate file extensions for our purposes. So the simplified Regexp allows using anything as the file name. It brings benefits for
*.js*matching bothjsandjsxfiles for instance.Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?) No.
Other information: