Filter on reference fields about rest-layer HOT 1 OPEN

As a first warning, there isn't much active development of rest-layer. We for one have decided to use it more or less, as-is, and the original author, @rs, is not using this project in production.

That said, you are welcome to attempt to create a PR four your use-case. Before you start on the code though, there are some considerations to take:

1. How do you find the related resource for Filter validation in the schema package (with no knowledge of the resource package)? Do you define a better interface for finding related resources?
2. Do you always allow filtering of related resources, or do need to configure it in the schema?
3. How do you implement this within the resource pacakge and/or within the resource Storer implementations?

Implementation wise, as there are no joins available in the rest-layer abstraction, there would need to be two distinct queries when doing related lookup. E.g. first get all companies, then extract the IDs, and then do the final query.

For example, if a user has just permission to see measurements related to a specific company, I can easily add a filter predicate to the query.

As for permissions, then you can do this with resource hooks today, as your own extension to rest-layer. Within the hooks, you can do as many sub-queries as you need. We have a permission system where we do perform related queries, compile the result into a new query for the target resource (usually an $in query), and finally join the permission query with the user query with an explicit AND.

from rest-layer.