saade / filament-laravel-log Goto Github PK

Hello,

Thanks for your package, it's really neat!

There is an error in the readme regarding the publish file command though:

php artisan vendor:publish --tag="filament-laravel-log-config"

This returned the following error message:
No publishable resources for tag [filament-laravel-log-config].

The command to publish assets for me were the following:

• php artisan vendor:publish --tag="log-config"
• php artisan vendor:publish --tag="log-translations"
• php artisan vendor:publish --tag="log-views"

I had to look for the proper one by using the generic 'vendor:publish' command, as you can see below:

Maybe I'm missing something, but here goes.

According to the documentation, I could do something like this:

FilamentLaravelLogPlugin::make()
  ->authorize(
      fn () => auth()->user()->isAdmin()
  )

However, the return from auth()->user() is always null. Apparently, in the life cycle, the providers are analyzed before the laravel framework retrieves the authenticated user's data.

Therefore, there is no way to do any checking there, since the user is not yet available.

Am I forgetting something or is there a bug here?

Hi,

Thanks for creating this plugin, I believe it's very useful!

One thing I discovered is when I add this callback for the authorize() method an Exception is thrown:

        ->authorize(
            fn () => auth()->user()->hasRole('super_admin')
        ),

This is the Exception:

Any clues on why this is happening?

Hello, this is a very nice package.

However, I am unable to set custom log directories using the given method. It just falls back to the default "logs".

Has anyone else faced the same issue before?

Basically, this is how I have implemented it. Each of the two directories has one log file. Neither is seen.

I believe the Facade \Saade\FilamentLaravelLog\Facades\FilamentLaravelLog isn't set up correctly because composer complains about it every time when it updates files for my IDE Helper:

> @php artisan ide-helper:generate
Exception: Target class [filament-laravel-log] does not exist.
Skipping \Saade\FilamentLaravelLog\Facades\FilamentLaravelLog.
Exception: Target class [filament-laravel-log] does not exist.
Skipping \Saade\FilamentLaravelLog\Facades\FilamentLaravelLog.

Is the Facade actually needed or useful?