One-to-many link not consistently returning objects in the correct order

Grapher appears to be inconsistent with how it treats the ordering of one-to-many links.

If I have a Post document like this:

const myPost = {
  commentIds: ['id1', 'id2'],
};

And a link between my Posts and Comments collection, I expect any grapher query to always return the 2 comments in the same order:

const myGrapherPost = {
  comments: [{ _id: 'id1', ...moreData1 }, { _id: 'id2', ...moreData2 }],
};

However I’ve started seeing some queries come back with a different order, like this:

const myGrapherPost = {
  comments: [{ _id: 'id2', ...moreData2 }, { _id: 'id1', ...moreData1 }],
};

It’s pretty hard to trace down, but I have this happening for 2 similar queries on the same collection, one with pure MongoDB data, and the other with an async Reducer fetching stuff from a third party API.

Is there a check somewhere that makes sure arrays are always ordered properly?

[theodorDiaconu]

@Floriferous yes ofcourse, but like this:

Posts.createQuery({
   $options: { sort: { createdAt: -1 } },
   comments: {
        $options: { sort: { createdAt: -1 } },
   }
})

[Floriferous]

Is it possible that this nested $options can only go one level deep?

I’m getting an uncaught error: MinimongoError: Projection values should be one of 1, 0, true, or false when adding $options in one of my shared “fragments” across collections.

i.e. is something like this allowed ?:

Posts.createQuery({
   $options: { sort: { createdAt: -1 } },
   comments: {
        $options: { sort: { createdAt: -1 } },
        message: 1,
        linkedPosts: { // Link to Posts
          $options: { sort: { createdAt: -1 } } 
          comments: { message: 1, $options: { sort: { createdAt: -1 } } }
       }, 
   }
});

What else could be causing this issue?