Tree view should load one level of subfolders in one HTTP request

The tree view issues multiple requests to get info about the server view:
GET https://one.ubuntu.com/files/api/folders/
[{"share_id": null, "type": "folder list", "value": ["fca0082b-3eb7-49ad-abf7-113fa2d6b570", "shared_with_me"], "context": ""}]

Then for each "value" a new request is created.

Imagine a folder with 200 subfolders:
[{"share_id": null, "type": "folder list", "value": ["51c8c904-543f-45ab-bf23-72dace1eeaee", "d1bf81ad-ca99-41ad-b5ed-e96ef6ea10a5", "cb6b3a65-9118-434b-a78d-6701216e3fea", "372174d5-99ce-453c-9731-6c58d45a0db1", "8d24b9f8-a962-4c93-b4fb-6048d98f9c51",
...
 "9a734f89-6ff1-4f5d-a3ac-ce1aa2a049d1", "d05e0cfb-a0f9-4268-801c-b32190ee7ab3", "4ec661e6-f29a-41c0-b2a6-21530daa0db8"], "context": "8547a9a8-be70-42ef-b363-cb6c4e2ecac6"}]

For each folder a new request will be created, leading to a massive amount of HTTP calls.
Some of them might never complete (like for the first time), some will give the user '03:13:54 PM (1ms): network: Error parsing json: ' message (in console log) thus leading to an incomplete view. 304 response helps a bit, but it should be given for each and every file and folder.

Since the server knows all the structure already, it is possible to eliminate such amount of traffic/requests by providing a single request/response for every nesting level.