Core: Extract IRIFilter from SearchFilter?

[teohhanhui]

Filtering by IRI or ID can be made more explicit.

This will make things clearer and also has the potential to fix a use case in #70 (i.e. null means no value for a to-one relation).

[teohhanhui]

Further thought: Perhaps it can be made into a relation filter, where we can also query whether a specific related resource is contained / not contained in the collection (through a to-many relation).

[dunglas]

Looks fair enough.

[theofidry]

Are you talking about SearchFilter::getFilterValueFromUrl()?

[teohhanhui]

@theofidry No. I'm talking about "filtering on relations".

[Simperfit]

@teohhanhui We can filter on relations with all of the filters, it is still an issue ?

[teohhanhui]

@Simperfit This issue is about separating the relation filter from the
string matching filter, because they're unrelated.

On 7 Nov 2016 19:10, "Amrouche Hamza" [email protected] wrote:

@teohhanhui https://github.com/teohhanhui We can filter on relations
with all of the filters, it is still an issue ?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/api-platform/core/issues/319#issuecomment-258808625,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAhf69P20bjMPgSyGQbuOdgloVam3Bvwks5q7wcQgaJpZM4GaAxX
.

[Simperfit]

I forgot about this. I think this should be done, and I think we will do it. But it means alot of deprecation.