Support for wildcard/ignore-case

[schenksj]

What is your idea?

It would be awesome to have a case-insensitive wildcard. Curious of the communities thoughts. On the surface, it doesn't seem like a tough implementation, though I'm not terribly confident in the syntax given that we were trying to avoid an ignore-case keyword...

{
  "detail": {
    "command_path": [  {"wildcard":  {"ignore-case": "*/Cmd.exe*"}  } ]
  }
}

The above matches stufff/cmd.exe -x stuff/Cmd.exe -x StUff/CmD.ExE .

Would you be willing to make the change?

Probably

Additional context

Add any other context (such as images, docs, posts) about the idea here.

[baldawar]

we can change ignore-case to ignore-case-equals for the sake of consistency, but I have the similar performance concerns as mentioned in #72. I worry that this'll be diminishing returns.

For your use-case, are there any constraints on performance / match-time / rule compile time ? If so, we'd have to consider the effort tied to it (esp if you expect many wildcards to be use for a single key).

[youngm]

We just ran into the need for this use case. In our case, we have no constraint on performance /match-time / rule compile time.

I don't think this is high enough of a priority for me to provide a PR just yet. But, I'd like to give another vote for considering this.

[baldawar]

I'm currently looking into simplifying how matchers interop with each other. If everything goes as planned, we'd be able to deliver this as well without any compromises on performance.

[vincen7tran]

hi all,

is the support for wildcard + equals-ignore-case coming anytime soon? or are there work arounds?

thanks