Unnecessary data in a Job class

[Manriel]

Probably, we don't need to push the LogToDb main class into the Job here

laravel-log-to-db/src/Jobs/SaveNewLogEvent.php

Line 22 in 026a492

public function __construct(protected object $logToDb, protected LogRecord $record)

Passing the class instance into the Job is causing to have an additional data of that class in json-serialized representation of the job in redis/db/whatever job storage it use.

At the same time we always could get a LogToDb class instance right inside the job's handle method without performance cost.

So, right now in a waiting jobs we just waste RAM to store copies of identical data which recoverable without job-specific context.

[danielme85]

I see what your saying, agreed. Probably don't need to serialize the whole object. I prob just followed the Laravel doc back in the day :p

Feel free to suggest a PR, or I'll look at it when I have some time.

[Manriel]

#70 should fix this

[danielme85]

merged into main, thanks!