Added support for basic glob patterns in "inputFile"

[mrcrowl]

This allows the "inputFile" attribute of each config to include the glob
characters: *?

Any file which matches the glob pattern will be compiled. The
"outputFile" attribute is ignored and instead the sourceFile's path is
used as the output file, but with the extension changed to the compiled
extension. e.g. less --> css

Saving the compilerconfig.json currently does not compile all matching
files in the project.

[304NotModified]

that looks a bit tricky.

edit: I see it was already there

[madskristensen]

Shouldn't it work like this:

If outputFile is a folder name, compile each file found in inputFile globbing and dump the resulting .css files in that folder. If outputFile is indeed a file name, then concat the entire output into that single file

[mrcrowl]

I'm unsure. What I read from the comments in issue #49 is that your users
are primarily looking to restore the behaviour that was present in Web
Essentials 2013, where a css file would be generated in the same directory
as the less file lives. This is certainly what I was after.

Perhaps other could comment on their perspective?
On Tue, 22 Mar 2016 at 4:39 AM, Mads Kristensen [email protected]
wrote:

Shouldn't it work like this:

If outputFile is a folder, compile each file found in inputFile globbing
and dump the resulting .css in that folder. If outputFile is indeed a
file name, then concat the entire output into that single file

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#199 (comment)

[longzheng]

+1 a way to restore Web Essentials 2013 functionality of auto compiling all files in the same directory with the same filename.

[damiangreen]

yes please +1

[304NotModified]

+1

[larsendaniel]

Another +1 vote! This is sorely needed.

[304NotModified]

@madskristensen What should be changed to get this merged/accepted?

[madskristensen]

@304NotModified it contains conflicts that prohibits me from merging the PR.

[LordJZ]

Wow, it's surprising to see this very basic regression not being fixed in almost 2 years.

[304NotModified]

I can rebase this (and create a new PR), could someone test it?

[mrcrowl]

Personally, I gave up and moved to vs code (and built the EasyLESS extension for it instead)

…

On Tue, 4 Jul 2017 at 8:41 AM, Julian Verdurmen ***@***.***> wrote: I can rebase this (and create a new PR), could someone test it? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#199 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABtooIX0-nTfPrEaQO5BWApfqLnZYVCiks5sKVHbgaJpZM4H0-a8> .

[304NotModified]

VS code is nice, but it's a bit pain to use 2 IDEs (VS + VS code), also we need this on the CI server.

[LordJZ]

I am rebasing this right now and will test.

[304NotModified]

👍