Skip to main content

Files

Qore\Next\System\Models\File stores uploaded file metadata and links the physical file to the model that owns it.

Most applications should interact with files through FileField, not by creating File models directly.

What The Model Stores​

File uses a UUID primary key and stores:

  • disk, path, filename, mime_type and size for storage;
  • name for the field name that uploaded the file;
  • user_id for the uploading user;
  • entity_type and entity_id for the owning model;
  • delete_at for temporary uploads that should be cleaned up if they are never attached.

The computed url attribute points to the file view route:

$file->url; // route('files.view', $file->id)

Upload Flow​

Uploads go through FileController::store():

  1. The request resolves the resource, model and field when available.
  2. If the field uploads files, Qore checks max file size and allowed MIME types.
  3. A File record is created with delete_at set a few hours in the future.
  4. The FilePolicy upload check runs.
  5. The uploaded file is stored on disk.
  6. The frontend receives FileJsonResource.

The temporary delete_at value matters because a user can upload a file before the parent form is submitted. If the parent form never saves, the file can be deleted later.

warning

Uploads and downloads are not authorized by the field alone. app/Policies/FilePolicy.php controls whether the current user may upload or view a file. Check upload() when a FileField upload is rejected, and check view() when an uploaded file cannot be opened.

Attaching Files To Models​

Models that use FileField must implement ModelWithFiles and use HasFiles:

use Illuminate\Database\Eloquent\Model;
use Qore\Next\System\Model\HasFiles;
use Qore\Next\System\Model\ModelWithFiles;

class Project extends Model implements ModelWithFiles
{
    use HasFiles;
}

FileField attaches files during lazy mutation, after the parent model has been saved:

  • removed file IDs are deleted;
  • new file IDs are associated to the model;
  • delete_at is cleared for attached files;
  • the change is written to the resource logbook.

Viewing Files​

FileController::view() finds the file, authorizes view, then serves it from the configured disk.

Images and PDFs are displayed inline. Other MIME types are downloaded with X-Content-Type-Options: nosniff.

Deleting Files​

When a File model is deleted, the model event also deletes the physical file from storage if it exists.

That means application code should delete the File model instead of only deleting the disk object.