diff options
author | Paul Grayson <paul@pololu.com> | 2015-08-14 15:19:56 -0700 |
---|---|---|
committer | Paul Grayson <paul@pololu.com> | 2015-10-29 17:02:13 -0700 |
commit | e6e056c2c141ec94eb8e79a30ee766f77fdaf30d (patch) | |
tree | 789818a9cc7efaa96a6f2d5e36dbbf3d81daaeb3 /railties/exe | |
parent | 8941831733fc56e2b1872f41c85cc48d782bb984 (diff) | |
download | rails-e6e056c2c141ec94eb8e79a30ee766f77fdaf30d.tar.gz rails-e6e056c2c141ec94eb8e79a30ee766f77fdaf30d.tar.bz2 rails-e6e056c2c141ec94eb8e79a30ee766f77fdaf30d.zip |
In url_for, never append ? when the query string is empty anyway.
It used to behave like this:
url_for(controller: 'x', action: 'y', q: {})
# -> "/x/y?"
We previously avoided empty query strings in most cases by removing
nil values, then checking whether params was empty. But as you can
see above, even non-empty params can yield an empty query string. So
I changed the code to just directly check whether the query string
ended up empty.
(To make everything more consistent, the "removing nil values"
functionality should probably move to ActionPack's Hash#to_query, the
place where empty hashes and arrays get removed. However, this would
change a lot more behavior.)
Diffstat (limited to 'railties/exe')
0 files changed, 0 insertions, 0 deletions