Feature Request: built in support for non where/in filtering

Out of the box, JR takes this:

GET /users?filter[first_name]=Yehuda

and turns it into the equivalent of this:

User.where(:first_name => ["Yehuda"])

Although JSON API spec is agnostic about filter implementation, I propose introducing some naming patterns for "starts with", "ends with", "contains", and "not in" type attribute filters.

Examples

Get all users with a first_name that starts with "ye":

GET /users?filter[first_name^]=ye

Get all users with a first_name that ends with "huda":

GET /users?filter[first_name$]=huda

Get all users with a first_name that contains "hud":

GET /users?filter[first_name~]=hud

Get all users with a first_name that is NOT "Yehuda":

GET /users?filter[first_name!]=Yehuda

Rastrea el procesamiento existente de GET /users?filter[first_name] hasta su conversión a User.where. Revisa cómo se analizan los nombres y valores de los filtros y, a continuación, determina el comportamiento esperado para los filtros starts-with, ends-with, contains y not-equal. Se considerará terminado cuando las cuatro formas de consulta propuestas sean compatibles y cuenten con cobertura correspondiente.