The feature is being described as bringing back the old legacy view for Folder View. It clearly does not do that. It is a bug. This is not "it doesn't work as I want it to"; It is that it does not do what it is described to do, iow duplicate the way it has worked for years. The feature does not work as the 4.8 and earlier Folder View did. Period. It is close, but is not recreating the legacy behavior as advertised. This is a beta feature and bug reports against it allow them to get it right. Please stop being an apologist for the facts that the devs did not consider some scenarios. The purpose of reporting issues is so they can present as polished a product as possible.
Again, the code to do this is in the app already otherwise my old folders, which were created 4.8 or earlier, would not be working, but they are. All we are asking for is to just have the option for it to continue to work as it always has. I do not understand why you think that continuing to use the existing code to pick an image from the sub folders is somehow complex and performance hinfdering since it has done this for years and years without being either. iow the exact same code being used to pick an image from the sub folders can be used for picking an image from the images associated with the sub folders for a given N folder structure and associating that image with the parent folder is so complex or performance-hending.
This is a freshman-level assignment to walk a direcotry tree. It is neither complex nor time-consuming. It is well within the capabilities of the developers to do (again, there is already code in the server doing this). Unless they know that there are scenarios they did not consider or test, how can they fix the product to the best it can be?