You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use a module that frequently makes updates to the api's query builders to add in or process an additional parameters from the module. Because findResourcesFromPropertyIds doesn't go through the API, we aren't able to extend our module's functionality to this extremely useful feature. Is it possible to add an event that contains the querybuilder, similar to the events in the API after the query is built but before it is executed, e.g. here
The text was updated successfully, but these errors were encountered:
Hi @zerocrates! I'm on parental leave till around April but here is the best of my recollection:
The module I referenced creates "teams" that are bundles of users/resources/sites, and then it controls what users can do and see within each team where they are a member. It is similar to the WordPress multisite interface, if you are familiar with that, where a single user can belong to multiple WordPress sites inside the multisite installation and have different roles in each site.
What I would like to be able to do is to enforce those "team" boundaries within the findResourcesFromPropertyIds query so that only resources within a given team are returned. Elsewhere in the module I have been adding a left join on the resource results with the team's resources, and that was the pattern I envisioned using here.
If there is a better or easier way to implement I'm totally open to that as well!
We use a module that frequently makes updates to the api's query builders to add in or process an additional parameters from the module. Because findResourcesFromPropertyIds doesn't go through the API, we aren't able to extend our module's functionality to this extremely useful feature. Is it possible to add an event that contains the querybuilder, similar to the events in the API after the query is built but before it is executed, e.g. here
The text was updated successfully, but these errors were encountered: