Closed tmeasday closed 8 years ago
I'm thinking about any time the sort order is not knowable on the client. For instance if you query a fulltext search endpoint (think ElasticSearch) to get a ranked set of documents for the publication.
You can just pass that extra score to the client in that case. See the example here: https://github.com/peerlibrary/meteor-subscription-scope
Well sure if you are ok about adding extra fields to the document. What I was thinking about was something similar to what you've done where the extra field is stripped somehow before coming back out to the query-er
Yes, but that score field is something you might even want to display to the user. Anyway, those are details. I am explaining my rationale. :-) As you noticed, it is something easy to change. And also I on purpose on the client side check only for existence of the field so that in theory we can add any extra payload.
Article outline
https://github.com/meteor/guide/blob/master/outlines/data-loading.md
Major decision points
publish-composite
Old outline:
Proposed outline
Open Questions