DASH Content browser for large projects (with huge ammounts of folders with assets)
Hey Dash Team, I'm happy working with Dash, but I was never able tu use the Dash content browser with my big large projects so here we go again 
I noticed, in small projects the content browser will compute just fine (because I have 5 folders with 200 assets each). But in large projects, when I try to scan 1 folder, it will somehow try to compute or analize all the folders (lets say 1000 folders with around 200 assets each) first, like, Dash thinks I want to compute the entire 1000 folders, leading to crashes and bootlenecks.
Maybe, there should be a way to let the content browser analize and compute 1 folder actually instead go to the 1000 folders and the 200 assets in each folder, and then, scan the folder I want, making the compute process stable, reliable and fast.
I think Dash gets all the folders and assets in each compute of a project, instead the folder we want, that why the compute process is actually slow.
My only workaround was to split my huge project in very small projects, but takes a lot of time and doesn't feel right.
I noticed, in small projects the content browser will compute just fine (because I have 5 folders with 200 assets each). But in large projects, when I try to scan 1 folder, it will somehow try to compute or analize all the folders (lets say 1000 folders with around 200 assets each) first, like, Dash thinks I want to compute the entire 1000 folders, leading to crashes and bootlenecks.
Maybe, there should be a way to let the content browser analize and compute 1 folder actually instead go to the 1000 folders and the 200 assets in each folder, and then, scan the folder I want, making the compute process stable, reliable and fast.
I think Dash gets all the folders and assets in each compute of a project, instead the folder we want, that why the compute process is actually slow.
My only workaround was to split my huge project in very small projects, but takes a lot of time and doesn't feel right.
