id column not receiving array for custom ransacker

[johnrees]

I have a ransacker called :student_users and use the filter student_users_in

I've simplified the code below to try and show what is happening

ransacker :student_users, :formatter => proc { |v|
  [10,11]
} do |parent|
  parent.table[:id]
end
...
SELECT DISTINCT "users".* FROM "users" WHERE "users"."id" IN (NULL)

I'd expect the above to return SELECT DISTINCT "users".* FROM "users" WHERE "users"."id" IN (10,11)

If I return an integer in the proc then it behaves as I'd expect

ransacker :student_users, :formatter => proc { |v|
  10
} do |parent|
  parent.table[:id]
end
...
SELECT DISTINCT "users".* FROM "users" WHERE "users"."id" IN (10)

If I filter the first_name (string) field instead of id, it shows that the array is actually getting passed from the proc

ransacker :student_users, :formatter => proc { |v|
  [10,11]
} do |parent|
  parent.table[:first_name]
end
...
SELECT DISTINCT "users".* FROM "users" WHERE "users"."first_name" IN ('---
- 10
- 11
')

Have I misunderstood something here?

[ideanl]

I am experiencing the same issue, and have looked through the source a bit, but I'll keep digging for the bug. It appears that the first name is being passed in incorrectly, so that's also an issue right? I feel like this is a result of Arel updating to 6.0.

[jonatack]

@johnrees, @ideanl, thanks for the issue. The first step would be to contribute a test for the problem. A test helps others reproduce the issue easily and work efficiently to solve it.

[jonatack]

Update: #486 fixes compatibility with Arel 6.0. Filtering on a string field instead of id as per the OP's last example is still not working.

[ideanl]

Filtering on a string field works now in PR #488

[jonatack]

Great job! Closing this.