I stumbled across this issue when calling .facet(..., filtered=True) on a query that did not have a filter. I'd say that the API should be robust and accept this usecase, especially since you can set up a pipeline that chains various calls on an S() object and ends up calling facet on it.
I stumbled across this issue when calling .facet(..., filtered=True) on a query that did not have a filter. I'd say that the API should be robust and accept this usecase, especially since you can set up a pipeline that chains various calls on an S() object and ends up calling facet on it.