Ecto order_by

Show us how you construct the Ecto query?

def list_posts(criteria \\ %{}) do
    {sort_by, sort_order} = sorters(criteria) || {:name, :asc}

    from(p in Post)
    |> order_by({^sort_order, ^sort_by})
    |>Repo.paginate(
      query,
      [
        before: Map.get(criteria, :before_cursor),
        after: Map.get(criteria, :after_cursor),
        cursor_fields: [{sort_by, sort_order}, :id],
        limit: Map.get(criteria, :limit, 10)
      ])
end

defp sorters(%{sort: %{sort_by: sort_by, sort_order: sort_order}}) do
    {sort_by, sort_order}
  end

I call the function like this Posts.list_posts(%{sort: %{sort_by: :type, sort_order: :desc}, limit: 2})

In this case, yes. However sorting by tuple is non-standard behaviour and instead you should provide list of fields instead, so it will be more SQL standard conformant.

Do you mind giving more clarity on how it is able to sort by both fields(type and name) when only type is given as sort_by?