Describe your idea, in simple words.
I want an endpoint that I can pass a pattern and then get back a list of patterns that kupo already tracks and match this pattern.
Why is it a good idea?
I query many different addresses in my application. It might happen that one of the addresses I am interested about is not tracked by kupo, in that case I want to fall back to a different endpoint. Rather than querying all patterns from kupo and then comparing them inside my application, it would be simpler to provide such a functionality inside kupo.
Are you willing to work on it yourself?
Yes, however I have trouble testing this. There is a prototypical implementation of this here: master...nielstron:kupo:master
I however have not been able to test if it works as intended (or even compiles)
Describe your idea, in simple words.
I want an endpoint that I can pass a pattern and then get back a list of patterns that kupo already tracks and match this pattern.
Why is it a good idea?
I query many different addresses in my application. It might happen that one of the addresses I am interested about is not tracked by kupo, in that case I want to fall back to a different endpoint. Rather than querying all patterns from kupo and then comparing them inside my application, it would be simpler to provide such a functionality inside kupo.
Are you willing to work on it yourself?
Yes, however I have trouble testing this. There is a prototypical implementation of this here: master...nielstron:kupo:master
I however have not been able to test if it works as intended (or even compiles)