Support for anything-but - suffix - equals-ignore-case

[SamD]

I was hoping to see that I could check a suffix with equals-ignore-case however that doesn't seem to be the case.

I see that anything-but on a suffix is supported

{
  "detail": {
    "instance-id": [ { "anything-but": { "suffix": "1234" } } ]
  }
}

However equals-ignore-case is not

"FileName": [
  {
    "anything-but": { "suffix": {  "equals-ignore-case": ".png" }
    }
  ]
}

``

Were there any plans to support this ?

Thanks

[omwanere]

Hi @SamD, thanks for raising this enhancement.

I'm new to the project but would like to work on adding support for
equals-ignore-case inside anything-but + suffix.

I'll start by adding a test case and exploring the pattern matcher implementation.
Please let me know if this is still open for contribution.

[timbray]

Oops, sorry, replied to wrong thread. -T

…

On Jan 25, 2026 at 11:31:11 AM, Tim Bray ***@***.***> wrote: That’s better. I still find it a bit puzzling that in both examples, the descriptive language talks about “foo-a”, “foo-b”, and “foo-c” but the “foo-“ names don’t appear in the example. It’s not obvious what the relationship is between the module name (e.g. “A”) or namespace ("urn:ietf:params:xml:ns:yang:A”) and the foo-a “container” name. But this may just be because I’m not familiar with the application domain. -T On Jan 25, 2026 at 1:12:28 AM, Om Wanere ***@***.***> wrote: > *omwanere* left a comment (aws/event-ruler#236) > <#236 (comment)> > > Hi @SamD <https://github.com/SamD>, thanks for raising this enhancement. > > I'm new to the project but would like to work on adding support for > equals-ignore-case inside anything-but + suffix. > > I'll start by adding a test case and exploring the pattern matcher > implementation. > Please let me know if this is still open for contribution. > > — > Reply to this email directly, view it on GitHub > <#236 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAAEJE4UD5VBQBA6MUGBAOD4ISCHZAVCNFSM6AAAAACL6B4H76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOJWGI2TAOJTG4> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >

[SamD]

@omwanere

Thanks for the update.
I am no longer involved in the original project that led to this question and I did find a workaround. However the library was helpful and supporting additional query types would be helpful for new comers.