Hi @Greg_K.
This is making it very complex and, I think, requiring lots of unnecessary API calls.
When a new folder is uploaded, I need to make a playlist from the mp3 files and share it.
So I detect when the folder is likely to be "settled" by seeing if the most recent file is older than 5 minutes. At which point I run
sharingCreateSharedLinkWithSettings for each file to generate a playlist to save an API call each time.
But what if an item gets added, removed or changed? There is no way of knowing which item, so I have to run the create link on all the items, each time, with
result.url...
or "catch" the error, and then look for result.error.error.shared_link_already_exists.metadata.url
To have content_hash on folders would be amazing and save all those calls!
(To have public-style folders back would be even more amazing!)
Unless I am missing a trick here?