Hi, Branden; On Fri, Sep 30, 2022 at 02:27:59PM -0500, G. Branden Robinson wrote: ... > I would suggest that these date-sorting fields in particular could be > handled as further "Additional constraint(s)" as the UI already > supports.
I've added another date operator, '*', to the existing '>', '=', '<', and made it default; let us hope the users will understand that it means 'any, even undefined.' > > > 7. Erasing the operator from the chunk of the HTTP GET query doesn't > > > work, possibly because there's no empty or null option for the date > > > ordering operator. It defaults to the first item in the list, which > > > is "<". (This appears to be true for both "date_op" and > > > "close_date_op".) You have to remove these chunks entirely. > > > > I don't understand how these are possible. ... > I simply > hand-deleted various "&foo=bar" fields until I was left with a query > that returned the results I sought. Now I see, thanks.
signature.asc
Description: PGP signature
