should we add some doc controls? about ponapi HOT 3 CLOSED

I think the filter param can handle the relationship part because the attributes and relationships keys are supposed to occupy the same namespace, so it naturally follows that the filter param is not just for filtering out attributes, but also relationships.

This does mean that we definitely need to hand the filter down to the DAO and let it handle these duties (no need to have it make additional DB calls for relationships that we don't want in the output, etc).

from ponapi.

I was referring to "I want this document without the relationship structure", not to filter resources based on relationship values.

The other one is also a good thing to do, so here is a list of ideas we can do:

1. support document-level control, so the client can force not receiving what it doesn't want (e.g. "no relationships, please")
2. support filtering based on relationship/links/included(?) values
3. (another idea) extend filtering syntax to indicate more than just exact values to match (syntax for expressing various operations: =,>,<,>=, <=,and,or,not...)

thoughts?

from ponapi.

We agreed that adding logic into the filters to support the various operators (filter[id:gt]=1 filter on IDs greater then 1) and passing this down to the DAO layer to do whatever makes sense for it.

from ponapi.