files/list_folder API returning subfolders before parent folders

Szymon D.

Most of the times the list_folder API returns parent folders before subfolders, but I've somehow managed to get it otherwise (I can't remember the sequence of folder operations that I performed, but it included moving, removing, un-removing and renaming). This is the example:

{ ".tag": "folder", "name": "abc", "path_lower": "/ttts/abc", "path_display": "/ttts/abc", "id": "id:l5CE9n6dddAAAAAAAAAACg", "shared_folder_id": "1188003718", "sharing_info": { "read_only": false, "shared_folder_id": "1188003718" } },

{ ".tag": "folder", "name": "ttts", "path_lower": "/ttts", "path_display": "/ttts", "id": "id:l5CE9n6dddAAAAAAAAAAEg" }

 

Is this normal to expect or rather an unexpected/buggy situation ?

Greg-DB

The order isn't guaranteed by /list_folder, so either way can occur. The guarantee is just that you'll get a correct representation of the state if your app processes all of the entries in the order given. Your app can then apply whatever sorting it wants once it has the entries.