Fix overlap lookup in subqueries.

[WaVEV]

fixes mongodb#209

This PR could be after arrayfield is merged.

[timgraham]

What do you think about a follow-up refactor that adds get_subquery_wrapping_pipeline() to the in/range/overlap lookup classes so these wrappers can be declared on the lookup rather than hardcoding/special casing lookup names in query(). It seems that would be a better separation of concerns.

[WaVEV]

It's a good idea, I will try to do in that way. El mié, 8 ene 2025 a las 11:39, Tim Graham ***@***.***>) escribió:

…

What do you think about a follow-up refactor that adds get_subquery_wrapping_pipeline() to the in/range/overlap lookup classes so these wrappers can be declared on the lookup rather than hardcoding/special casing lookup names in query(). It seems that would be a better separation of concerns. — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABO2S4QRLKRG6YCTAGB26R32JU2DVAVCNFSM6AAAAABUZBZ74CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZXHAZTKOBZHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[WaVEV]

What do you think about a follow-up refactor that adds get_subquery_wrapping_pipeline() to the in/range/overlap lookup classes so these wrappers can be declared on the lookup rather than hardcoding/special casing lookup names in query(). It seems that would be a better separation of concerns.

🤔 the idea is to call this getter in the Query.as_mql or in the in/range/overlaps/contains (yes this one will be added 😬 )
Or as a post process in in/range/overlaps/contains as_mql method?

[timgraham]

The first idea!