diff options
author | eileencodes <eileencodes@gmail.com> | 2017-08-01 15:10:51 -0400 |
---|---|---|
committer | eileencodes <eileencodes@gmail.com> | 2017-08-01 15:10:51 -0400 |
commit | 789f3be02048cf33c14c8a98c6fe91d0d7b157eb (patch) | |
tree | 2d7c8e28c03d83d6c15560048d4d4697f33d2f90 /actionview/test/tmp | |
parent | 9e3d8cbd0705cacf424ef4f99d2e317168442065 (diff) | |
download | rails-789f3be02048cf33c14c8a98c6fe91d0d7b157eb.tar.gz rails-789f3be02048cf33c14c8a98c6fe91d0d7b157eb.tar.bz2 rails-789f3be02048cf33c14c8a98c6fe91d0d7b157eb.zip |
Clarify route encoding test
Since this test changed in 9220935 I noticed that it really doesn't make
sense anymore. I split the tests into 2 groups to explain what each one
does.
First these routes should throw a `bad_request` when the encoding isn't
valid. We're expecting UTF8 encoding and passing binary, that should be
a bad request.
For the second test we are setting the `show` route to set
`self.binary_params_for?` for that route which will convert the
parameters and return a `:ok` instead of a `:bad_request`.
Diffstat (limited to 'actionview/test/tmp')
0 files changed, 0 insertions, 0 deletions