There may be a need to further filter the results right after executing the query.
In my case, I have a custom logic and I need to apply it to a contrib view, to filter its results.
I've considered the existing options:
\Drupal\views\Plugin\views\query\Sql class. This was my choice. The only problem I found is that the execute method is long and it performs many operations that I don't need to change.My proposal here is to discuss what is the best way to achieve the goal to filter results and if we can improve views to make it easier.
One improvement is needed is to breakdown the \Drupal\views\Plugin\views\query\Sql::execute method that is too long.
I also suggest enabling a new hook to allow filtering easily.
I'll submit patches with these suggestions after.
May be a new hook, hook_view_query_result. To be decided.
For now we only know that no backwards compatibility issues are foreseen.
Needs work
11.0 🔥
views.module
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
IMO you should use the 'views_post_execute' hook, AND the Sql class should be changed (not overridden - changed), since there are multiple issues with Full Pager and filtering after the SQL query.
The pager info should be generated AFTER the 'views_post_execute'.
I'm pruning all core issues with 'pager'/'pagination' and 'filter'. From all this crowd wisdom someone should have published the best way to correct the problem.