Criteria/properties order of MongoStore.query

[mkhorton]

I appreciate they're kwargs anyway, but is there a reason their order is reversed compared to pymongo? Think this might easily confuse people. (Also why query over find? for same reason)

[montoyjh]

Yes, this is on the list of todos, see #31. I think generally these were designed to reflect QueryEngine syntax. I'd prefer to keep query because it's similar to the rest interface and it's a bit distinct from find in that one can specify a list of properties as opposed to a dictionary for projection.

[mkhorton]

Ah, my apologies for creating the duplicate!

…

On Thu, Aug 23, 2018 at 23:17, Joseph Montoya ***@***.***> wrote: Yes, this is on the list of todos, see #31 <#31>. I think generally these were designed to reflect QueryEngine syntax. I'd prefer to keep query because it's similar to the rest interface and it's a bit distinct from find in that one can specify a list of properties as opposed to a dictionary for projection. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#37 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC1rRD8F2cKhsJgexLJae8TNExut28YQks5uT5plgaJpZM4WKuHq> .

[dwinston]

@montoyjh FYI one can specify a list of properties to a pymongo collection’s find, but in general I’d also like to have a different name for other abilities to mix in such as field aliasing (as MPRester.query does).