<@U01TR1SKEMP> This is fixed in `typesense/typesen...
# contributions
k
@Stefan Hesse This is fixed in
typesense/typesense:0.25.0.rc21
-- can you please give it a spin?