aboutsummaryrefslogtreecommitdiffstats
path: root/actionpack/test
diff options
context:
space:
mode:
authorPaul Grayson <paul@pololu.com>2015-08-14 15:19:56 -0700
committerPaul Grayson <paul@pololu.com>2015-10-29 17:02:13 -0700
commite6e056c2c141ec94eb8e79a30ee766f77fdaf30d (patch)
tree789818a9cc7efaa96a6f2d5e36dbbf3d81daaeb3 /actionpack/test
parent8941831733fc56e2b1872f41c85cc48d782bb984 (diff)
downloadrails-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 'actionpack/test')
-rw-r--r--actionpack/test/dispatch/url_generation_test.rb7
1 files changed, 7 insertions, 0 deletions
diff --git a/actionpack/test/dispatch/url_generation_test.rb b/actionpack/test/dispatch/url_generation_test.rb
index fd4ede4d1b..8c9782bb90 100644
--- a/actionpack/test/dispatch/url_generation_test.rb
+++ b/actionpack/test/dispatch/url_generation_test.rb
@@ -129,6 +129,13 @@ module TestUrlGeneration
)
end
+ test "generating URLS with empty querystring" do
+ assert_equal "/bars.json", bars_path(
+ a: {},
+ format: 'json'
+ )
+ end
+
end
end