Retrieve file from storage and cast it to UploadedFile

I don't think you can do that "out of the box" as (at a guess) it's calling is_uploaded_file() somewhere. You might be able to do something like :

class MyUploadedFile extends UploadedFile
{
  public function isValid()
  {
    return true;
  }
}

I'm guessing though :-) You could try passing the info to the constructor and see what happens I suppose :-)

Hey @ohffs ,

Thanks for your time, yeah you actually guide me in the right direction. I did it by initiating a new object from the constructor.

Here is a sample of my code, hope it can help someone in the futur.

    use finfo;
    
        $file_path = storage_path($filename);
        $finfo = new finfo(FILEINFO_MIME_TYPE);

        if (Storage::disk('local')->exists('path/' . $filename)) {

            return new UploadedFile(
                $file_path,
                $filename,
                $finfo->file($file_path),
                filesize($file_path),
                0,
                false
            );
        }

Yay - glad you got a solution :-)

Why would you ever do this?

@pmall

I need to extract some text from a stored file on update and I want my function to return a UploadedFile object mostly for code reuse because the extraction method is the same on create and on update.

I do this for maintenance purposes, so this way I can always be sure that I am working with a UploadedFile object through out the rest of the code. But you are right I could have done without it and maybe I will.

mostly for code reuse because the extraction method is the same on create and on update.

@chess So why dont you just extract this code into another class, and make a method taking a file as an argument to do this process (a file, not an uploaded file, this is more flexible, because an uploaded file is just an extended file). Then you can use this class anywhere you need to process a file, wherever it comes from.

A controller method (I guess it is what you want to reuse) is not made for code reuse / being called as a regular function, it is made for handling a request. But what's inside a controller can be reused anywhere if coded properly.

@pmall

" So why dont you just extract this code into another class, and make a method taking a file as an argument to do this process (a file, not an uploaded file, this is more flexible, because an uploaded file is just an extended file). Then you can use this class anywhere you need to process a file, wherever it comes from. "

Exactly what I did, this code was not for a controller method.

So why cant you make it work with both a file and an uploaded file ?