Currently, when something goes wrong with some of Ransack operations of Searching and Sorting, it raises an ArgumentError exception.
There is a sample on the docs:
Article.ransack(unknown_attr_eq: 'Ernie')
# ArgumentError (Invalid search term unknown_attr_eq)
I`m proposing here to change it to a custom error specific for Ransack operations because this error is a Ruby internal one specific for missing arguments on a method call.
Besides that, Ransack users will tend to rescue this error to render a response to the end user and it may lead us to a bad error supression.
Currently, when something goes wrong with some of Ransack operations of Searching and Sorting, it raises an
ArgumentError
exception.There is a sample on the docs:
I`m proposing here to change it to a custom error specific for Ransack operations because this error is a Ruby internal one specific for missing arguments on a method call.
Besides that, Ransack users will tend to rescue this error to render a response to the end user and it may lead us to a bad error supression.