You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In certain cases the .env config is not available for the blame to fall back on when calling getUserToBlamePk().
This results in a null result which immediately triggers an unhandled (and uncatchable) error exception as the return value has to be :string.
The solution would be to publish the system_user_id into the public config with a null default value and make it available for project-specific override (to avoid null calls).
It is a preferred Laravel pattern to use config() instead of env() anyways.
The text was updated successfully, but these errors were encountered:
zenoandras
added a commit
to Zenosyne-Technologies/laravel-blame
that referenced
this issue
Nov 19, 2024
In certain cases the .env config is not available for the blame to fall back on when calling getUserToBlamePk().
This results in a null result which immediately triggers an unhandled (and uncatchable) error exception as the return value has to be :string.
The solution would be to publish the system_user_id into the public config with a null default value and make it available for project-specific override (to avoid null calls).
It is a preferred Laravel pattern to use config() instead of env() anyways.
The text was updated successfully, but these errors were encountered: