diff options
author | Simon Courtois <scourtois_github@cubyx.fr> | 2018-09-27 19:51:57 +0200 |
---|---|---|
committer | Rafael Mendonça França <rafaelmfranca@gmail.com> | 2018-09-27 16:35:55 -0400 |
commit | d043920eb903d32a1e3540690d3b08d98d1b6d88 (patch) | |
tree | 647b6e3b4ac25e3ecd88b149fa8efbf96c811f46 /activesupport/README.rdoc | |
parent | d0d1cd3d45f14e8423ee8ee3f4c19e999a69b96c (diff) | |
download | rails-d043920eb903d32a1e3540690d3b08d98d1b6d88.tar.gz rails-d043920eb903d32a1e3540690d3b08d98d1b6d88.tar.bz2 rails-d043920eb903d32a1e3540690d3b08d98d1b6d88.zip |
Fixing an edge case when using objects as constraints
This PR fixes an issue when the following situation occurs.
If you define a class like this
class MyConstraint
def call(*args)
# for some reason this is defined
end
def matches?(*args)
# checking the args
end
end
and try to use it as a constraint
get "/", to: "home#show", constraints: MyConstraint.new
if its `matches?` method returns `false` there will be an error for the
mapper will ask for the constraint arity, thinking it is a proc, lambda
or method.
This PR checks for the presence of the `arity` method on the constraint
calling it only if present, preventing the error while keeping the basic
behavior.
Diffstat (limited to 'activesupport/README.rdoc')
0 files changed, 0 insertions, 0 deletions