Deeply nested folders sequence

[Mehonoshin]

Hi, folks!

I faced an issue with folder_from_path method.

When I have a deeply nested folders sequence, for example /1/2/3/4/5/6/7/8/9/10/.. and so on.
If I run folder_from_path, it runs an API request for each of these folders.

Such approach sometimes faces us with situation, when API calls limit is reached.
Another problem is that on 100 nested directories it takes too much time.

Maybe there is some workaround, or I could try to make PR with fix?

[cburnette]

Hey Stanislav, it's a known issue on the Box side that you have to walk the tree using their API to resolve a path by name. The Box engineering team is currently considering adding a new endpoint that will accept a path and do a quick resolution to folder or file id. I don't think it will be available in the next few months, however. For now I would employ a lot of caching on your end once you have resolved a path to an id.

[Mehonoshin]

Thanks for your response!

I've decided to change my app logic, to use id instead of path.