Rob Phillips

Thank you so much for the detailed response. This helps a ton. The part that I was missing to debug this on my own was the role of the `matcher`...

A better workaround is probably to `.join(',')` your ids to get a comma-separated string as shown here: https://github.com/feathersjs-ecosystem/feathers-objection#composite-primary-keys But yeah, the actual solution is probably to have this lib override...

I think the only way to do this is to fetch all the relevant data before building the ability. I'm currently handling this with service level hooks that make use...

Yes, I'm also using feathers-objection. As far as I know, the only way to limit fields on joined relations is to use a modifier. You can make these modifiers mandatory...

No worries! **tl;dr**: If your ability might change due to some user interaction, the current example setup in the docs will not work nicely with the socket.io transport. --- By...

It's a bit of kludge, but I'm really just stripping the default ability and recalculating it for every request on affected services. ```ts // service-with-dynamic-permissions.hooks.ts // remove the default ability...