You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: