GetTxsEvents query non-equals comparisons are blocked

[joe-bowman]

Summary of Bug

The GetTxsEvents endpoint expects all events will contain a = comparison, even though Tendermint itself supports >, >=, <, <= comparisons (indeed, the node.TxSearch comment specifies "tx.height > 5" as an example).

Version

v0.46.x

Steps to Reproduce

Submit a GetTxsEvents request, containing "tx.Height>5" and Cosmos rejects it for not matching the format "x.x=y", despite this being a valid event from Tendermint's PoV.

cosmos-sdk/x/auth/tx/service.go

Line 48 in 6081491

EventRegex = regexp.MustCompile(`^[a-zA-Z_]+\.[a-zA-Z_]+=\S+$`)

[alexanderbez]

Yes, the SDK's tx query proxy doesn't support Tendermint's proprietary operators -- it just supports direct comparison, i.e. =. @tac0turtle do we want to discuss supporting this? I mean we can just pass the user string directly to Tendermint, assuming Tendermint does proper input validation.

[tac0turtle]

might as well pass the input directly to tendermint. no need to validate on our end.

[alexanderbez]

might as well pass the input directly to tendermint. no need to validate on our end.

yeah that's what I'm proposing

[tac0turtle]

repeated what your said in agreement lol