Feature(s) impacted
Overriding route -
For my back office, I needed to customized the delete route of some of my tables to simultaneously delete my s3 associated bucket.
For instance, my users have their profile picture stored in s3: so I custom the delete route to force the s3 to be emptied at the same time.
I overrided both the delete and delete list route. In the delete list route, I had to rewrote everything iterating on each list member.
My first question is: is there a way to simply tell to the delete list override route to use the overrided simple element route? i.e. iterating on each list member and simply calling the delete route instead of having to rewrite everything.
My second question is similar:
My users have others related data, which also have s3 coresponding files. So for these related data, I’ve also overrided both the delete and delete list route.
Now, I want that when deleting a user, the related data are also deleted. This is correctly handled, but doesn’t use my override delete route for each related data. This means taht the related data are corrected destroyed, as well as the user s3, but, the related data s3 are not deleted.
Again, is there a way to force Forest to directly use the overrided route of the related data? Otherwise that I would have to, again, do manually the samed things on the delete user route, adding manually the delete of each s3 related data.
I hope my explanation was clear! I would be happy to provide more detail if needed.
Thanks a lot for your help,
Chloé.
Observed behavior
Forest overrided route are not used for related data.
Expected behavior
I would like to know if there is an option to directly force forest to use the override route of each related data.
Context
Forest & SQL