diff options
author | Aaron Kromer <aaron.kromer@gmail.com> | 2018-07-22 04:00:40 -0400 |
---|---|---|
committer | Kasper Timm Hansen <kaspth@gmail.com> | 2018-07-22 10:00:40 +0200 |
commit | 20543c049625784a91944efdebc1d0c397406f21 (patch) | |
tree | ef7dee42b0815dfafdfee1be0d7ad511f31468f4 /actionmailer/lib | |
parent | 76f22e19d6793c24a570f413e4f6b7b9b5416bf7 (diff) | |
download | rails-20543c049625784a91944efdebc1d0c397406f21.tar.gz rails-20543c049625784a91944efdebc1d0c397406f21.tar.bz2 rails-20543c049625784a91944efdebc1d0c397406f21.zip |
Add implicit to path conversion to uploaded file (#28676)
* Add implicit to path conversion to uploaded file
Ruby has a few implicit conversion protocols (e.g. `to_hash`, `to_str`,
`to_path`, etc.). These are considered implicit conversion protocols
because in certain instances Ruby (MRI core objects) will check if an
argument responds to the appropriate protocol and automatically convert
it when it does; this is why you can provide a `Pathname` instance into
`File.read` without having to explicitly call `to_s`.
```ruby
a_file_path = 'some/path/file.ext'
File.write a_file_path, 'String Path Content'
File.read a_file_path
a_pathname = Pathname(a_file_path)
File.write core_file, 'Pathname Content'
File.read a_file_path
core_file = File.new(a_pathname)
File.write core_file, 'File Content'
File.read core_file
tmp_file = Tempfile.new('example')
File.write tmp_file, 'Tempfile Content'
File.read tmp_file
```
So how does an uploaded file work in such cases?
```ruby
tmp_file = Tempfile.new('example')
File.write tmp_file, 'Uploaded Content'
uploaded_file = ActionDispatch::Http::UploadedFile.new(tempfile: tmp_file)
File.read uploaded_file
```
It fails with a `TypeError`:
no implicit conversion of ActionDispatch::Http::UploadedFile into String
In order to make an uploaded file work it must be explicitly converted
to a file path using `path`.
```ruby
File.read uploaded_file.path
```
This requires any code that expects path/file like objects to either
special case an uploaded file, re-implement the path conversion protocol
to use `path`, or forces the developer to explicitly cast uploaded files
to paths. This last option can sometimes be difficult to do when such
calls are deep within the inner workings of libraries.
Since an uploaded file already has a path it makes sense to implement
the implicit "path" conversion protocol (just like `File` and
`Tempfile`). This change allows uploaded file content to be treated more
closely to regular file content, without requiring any special case
handling or explicit conversion for common file utilities.
* Note uploaded file path delegation in CHANGELOG
Diffstat (limited to 'actionmailer/lib')
0 files changed, 0 insertions, 0 deletions