Currently OUTER is handled in the core and allows to refer to the query root of a parent query builder. Within entity views this might not be what people expect. This is only problematic when the subquery provider is in a subview which is why nobody complained too much yet. We should adapt that so that OUTER refers to the embedding entity view i.e. the entity view that uses the subquery provider instead. Referring to the entity view root which is what OUTER does right now can be done by using VIEW_ROOT. Since the entity view root could be changed, we might want to consider adding another macro called QUERY_ROOT that always refers to the query root.
We should document that using OUTER in a subquery within a subquery provider will still resolve to the embedding entity view.
Currently
OUTERis handled in the core and allows to refer to the query root of a parent query builder. Within entity views this might not be what people expect. This is only problematic when the subquery provider is in a subview which is why nobody complained too much yet. We should adapt that so thatOUTERrefers to the embedding entity view i.e. the entity view that uses the subquery provider instead. Referring to the entity view root which is whatOUTERdoes right now can be done by usingVIEW_ROOT. Since the entity view root could be changed, we might want to consider adding another macro calledQUERY_ROOTthat always refers to the query root.We should document that using OUTER in a subquery within a subquery provider will still resolve to the embedding entity view.