with_any_role(:role1, :role2) on User Object returns Array instead of ActiveRecord::Relation

[FreeApophis]

with_any_role(:role1, :role2) on User Object returns Array instead of ActiveRecord::Relation

This is a rather tiny issue, but it is rather surprising, since with_role already correctly returns a Relation Object which you can easily chain.
The problem showed up when I chained other Database scopes, and the temporary solution is to do the with_any_role at the end of the chain. This conflicts with other scopes like pagination, and of course the Array cannot be evaluated lazily.

[wldcordeiro]

Thanks for reporting this! We'll get this fixed up for the next release.

[fabn]

The same is true for with_all_roles. Is there any workaround?

[EppO]

You can combine ActiveRecord relations using .merge that combines WHERE clauses using AND which is not helping in that case (we need to OR the different WHERE clauses). With the upcoming Rails 5 release, we will be able to combine two ActiveRecord relation with OR (read this article for more info). I don't see any workaround for Rails <=4.x except playing with Arel directly.

[dkniffin]

Has there been any progress on this? I was really hopeful that this method would do exactly what I wanted, but then I saw it was an array, which prevented me from chaining it with other queries.