OrderBy url formed incorrectly about angular-odata HOT 2 CLOSED

That makes total sense, I didn't try the nested array, that completely works how I was expecting and forms the url correctly. Thank you!

It seems I may be one of the only other people using this library actively, so I am not expecting a fully documented app by any means - I am trying to read through your library code before posting 'issues' (not that this was actually an issue), I typically figure out what I need, this one just had me stuck. I still think this might be the most structured OData library for angular so far, especially in combination with the generator. If I see things I can fix I will definitely be doing that and send them your way.

from angular-odata.

the main intention for the orderBy was:

orderBy (string) where string is any string

orderBy ([keyof T, ...]) an array of entity fields (properties), where asc is the default value for all fields

orderBy ([[keyof T, 'asc' | 'desc'], ...]) an array of tuples (n = 2) where each tuple has the name of the property and the order asc or desc

PD: The project is lazy of documentation :(

from angular-odata.