is that just aggregating similar filters?
if that's the case, yeah, it does, i.e.
Component A:
`REQ, {kinds: [1], authors: [1]}`
Component B:
`REQ, {kinds: [1], authors: [2]}`
will result in query
`REQ, {kinds: [1], authors: [1, 2]}`
nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft does NDK do this?
https://void.cat/d/JFa1y11ifSqdd7NvT6BZPs.webp
Have i just wasted a bunch of time?
is that just aggregating similar filters?
if that's the case, yeah, it does, i.e.
Component A:
`REQ, {kinds: [1], authors: [1]}`
Component B:
`REQ, {kinds: [1], authors: [2]}`
will result in query
`REQ, {kinds: [1], authors: [1, 2]}`
what about the last 2 inputs though, they have same author but different kinds/limit would it merge them too?
I think it will different kinds but not different limits
I'm not 100% confident this code is super robust; I need to add more test cases to it
The problem im trying to solve is to actually diff the filters, but filters can be in any order or combination so in order to diff them i have to expand the filters into this "Flat" object first then diff the flat version and compress it again to get the diff result,
I think have it now but im wondering if its already been done
Expander does something like this:
What about nostr:npub1dcl4zejwr8sg9h6jzl75fy4mj6g8gpdqkfczseca6lef0d5gvzxqvux5ey does your lib do this?
Yes, it's documented. Sorry for not answering before :)