Wildcards no longer working for extension about log-highlight HOT 5 CLOSED

One more thing I noticed is that it doesn't like uppercase letters in filenames either.
For example it can match: "vm11-pl-4" but it cannot match "vm11-PL-4"

from log-highlight.

@eandmsz , I've updated to add wildcard for extension. About case-sensitivity, it makes filenames lowercase before comparing. I think it is good for Windows users.

from log-highlight.

@poucotm I have updated to 2.0.2.
If someone specifies "MESSAGES" in the config it will not match the filename "MESSAGES" because the filename gets converted to lowercase, but the pattern does not.
I think to make it properly case-insensitive you need to convert the patterns to lowercase as well. And maybe it worth mentioning in the comments that the matching is case-insensitive.

Regarding the wildcard: I'm not sure what I'm doing wrong but neither "messages*" nor "messages.*" pattern matches the filename "messages.1" for me.

from log-highlight.

@eandmsz, it works in my test as below (Windows 10).

"extension" : [ "messages.*" ], // case-insensitive

from log-highlight.

I'm also on Windows 10.
Okay now it works, I have no idea what made this error, but I have uninstalled/reinstalled all the plugins I had (FilterLines, SortBy, Log Highlight) and found that I had the "summary" : true, still left from 1.x.x config, so I removed that.

Thanks

from log-highlight.