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)
[x] Docs have been added/updated (for bug fixes/features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Improvement.
What is the current behavior? (You can also link to an open issue here)
The current documentation is a bit misleading. We have standard directories like the following:
/resources
/scss
/index.scss
/js
/index.js
When you use "./js/*/*.js", "./scss/*/*.scss" you miss files that are placed directly under js and scss directories.
So I think the most beneficial case is to not include the subdirectory pattern /*/.
What is the new behavior (if this is a feature change)?
I slightly changed that part of the documentation and added the correspond assert (if someone uses tests as documentation).
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, ...) Improvement.
What is the current behavior? (You can also link to an open issue here) The current documentation is a bit misleading. We have standard directories like the following:
When you use
"./js/*/*.js", "./scss/*/*.scss"you miss files that are placed directly underjsandscssdirectories. So I think the most beneficial case is to not include the subdirectory pattern/*/.What is the new behavior (if this is a feature change)? I slightly changed that part of the documentation and added the correspond assert (if someone uses tests as documentation).
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?) No.
Other information: