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

GET /users?filter[first_name] の既存の処理を User.where への変換まで追跡してください。フィルター名と値がどのように解析されるかを確認し、starts-with、ends-with、contains、not-equal フィルターに期待される動作を判断してください。4 つの提案されたクエリ形式が対応され、それに一致するカバレッジがあることを完了条件とします。