Details
-
Improvement
-
Resolution: Unresolved
-
High
-
None
-
None
-
None
Description
The current code in ezRecoServerFunctions::getRecommendations() presumes that recommendations always relate to 1 node.
But some scenarios, based on user behaviour, do actually work with no node id at all.
Being able not use use a node id in that case would avoid a few useless queries