I can use

orderBy

on the

dishes

but that seems to relate to the

Dish

entities (id, created, updated)

The solution is to have an intermediate type to represent the particular Dish on the Meal. So you'd have a type called something like MealDish which would have relationships with both Meal and Dish and would include the orderIndex field

Can you explain a bit more how that would work? Maybe writing pseudo queries? I already do something similar actually at another level, really when I said

Dish

it was a

Favourite

which has a link to

Dish

and

User

The MealDish type would have a 1-n relationship with Meal and a 1-n relationship with Dish, plus the orderIndex field

I would have to maintain

orderIndex

myself? or is that something offered by graph.cool?

No - you have to manage it yourself

I see, and then when I query, I’d do something like:

{
  allMeals {
    id
    date
    type
    mealDishes(orderBy: orderIndex_DESC) {
      id
      dish {
        id
        name
      }
    }
  }
}

(assuming they are not created simultaneously)

great

Or add an ordering (default 0) and a created by and order by both, that way default it will order on created date but you can overwrite it when needed 🙂

I'd do an ASC sort rather than DESC but that depends on how you are going to display the data I guess

for my use case, the order doesn’t actually change

ah, was just seeing if you actually could order on multiple values or not.. not sure how to do that, but I guess that's not an issue then

see the use case above

Yeah

but cheers both of you, seems like adding another intermediary entity is the way to go

As reference: Multi field ordering does not work yet: https://github.com/graphcool/feature-requests/issues/62

only negative is it becomes quite difficult naming things once you have to add a few levels of intermediary entities!

See: https://martinfowler.com/bliki/TwoHardThings.html 😉

haha