Add "check_parameters" option to "current_page?"

[mpugach]

Example:

For http://www.example.com/shop/checkout?order=desc&page=1

current_page?('http://www.example.com/shop/checkout')
# => true

current_page?(
  'http://www.example.com/shop/checkout',
  check_parameters: true
)
# => false

This is needed when http://www.example.com/shop/checkout navigation is also present on the page. Without this option both paths are considered current.

[rails-bot]

Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @sgrif (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

This repository is being automatically checked for code quality issues using Code Climate. You can see results for this analysis in the PR status below. Newly introduced issues should be fixed before a Pull Request is considered ready to review.

Please see the contribution instructions for more information.

[rafaelfranca]

Why this line is needed? Should not the keyword argument take care of this?

[mpugach]

not always

def ololo(options, some_keyword: false)
  puts options.inspect
  puts some_keyword.inspect
end

ololo(action: :index, controller: :some, some_keyword: :tralala)
# {:action=>:index, :controller=>:some, :some_keyword=>:tralala}
# false

[rafaelfranca]

Maybe check_paramters is a better name?

[mpugach]

@rafaelfranca, updated