Proposal for a usage of presenter pattern to solve a problem with one view per
ComputeResource all over the code base.
We have found an N+1 queries issue in Compute Resource vm listings . @Marek_Hulan has created a simple solution tested on vmware . In the process of reviews we found out that the solution will work just for some
We need a better control over the similarities and differences in
ComputeResources UI (presenting) and we can do so by introducing presenter pattern and encapsulate
ComputeResource UI differences in OOP fashion.
I have a little POC solving the issue described in motivation: github.com/ezr-ondrej/foreman/vmware_listing_performance