bezhansalleh / filament-exceptions

A Simple & Beautiful Pluggable Exception Viewer for FilamentPHP's Admin Panel

🥷 Hi! My name is Bezhan

I am a full-stack developer, mainly working with Laravel, TALL stack & VueJs. I work for Roshan as an Application Developer, building innovative Applications for Mobile and Web in Telecom Industry!

🔭 I'm currently working on...

• Roshan.af, a rebuild with Filament and Tailwind CSS.
• My Roshan app, providing customers an efficient way to stay connected through Afghanistan’s largest telecommunications service provider anywhere inside the country and beyond.

filament-exceptions's Issues

restrict `Exception` access to few roles only using `filament-shield`

I am trying to restrict access to Exception page to certain roles only using filament-shield i.e. admin but all the users are able to see and access it. is there any specific steps I need to follow apply generated policy to restrict access ?

composer require bezhansalleh/filament-exceptions error!

our requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires bezhansalleh/filament-exceptions ^1.0 -> satisfiable by bezhansalleh/filament-exceptions[1.0.0].
- bezhansalleh/filament-exceptions 1.0.0 requires bezhansalleh/filament-addons ^1.0 -> found bezhansalleh/filament-addons[dev-feature/chip-column, dev-main, v0.0.0, ..., 0.0.4] but it does not match the constraint.

Exception messages are not displayed

When exceptions are viewed, all relevant information are displayed except the message

Error with using multi tenant

Hey, can you add customization for isScopedToTenant in your exception resource. I need to give isScopedToTenant false.

Error

I have the next issue https://flareapp.io/share/dPb918Nm
I can't provide after what this was happened, because I missed the moment when it began to throw exception.

Not enough context

This really should be a feature request, but the feature request issue creation button currently displays error 404 (screenshot attached)

The exception should display the authenticated user (like Laravel Telescope does, screenshot also attached).

Error Occurs When `blade-icons.components.disabled` is set to `true`

After disabling the blade-icons components in favor of @svg blade directive, I'm encountering an error indicating missing components when using this package.

Here is the screenshot:

Install does not run or publish migrations

I had to publish the migrations manually to complete the installation.

Target class [Spatie\LaravelIgnition\Recorders\QueryRecorder\QueryRecorder] does not exist.

Using composer install --prefer-dist --no-dev -o for production.

Package spatie/laravel-ignition only available for development.

SPA mode: No line numbers or syntax highlighting

Hi! I've noticed a problem with SPA mode. Line numbers and syntax highlighing aren't visible when viewing an exception. Refreshing the browser while on the exceptions page fixes the issue. I'm guessing the problem is that the assets aren't being loaded when using wire:navigate to navigate to the exceptions page.

Laravel 11 Error Handling

In Laravel 11 ExceptionHandler removed
What i do?

<?php

namespace App\Exceptions;

use BezhanSalleh\FilamentExceptions\FilamentExceptions;

class Handler extends ExceptionHandler
{
    ...

    public function register()
    {
        $this->reportable(function (Throwable $e) {
            if ($this->shouldReport($e)) {
                FilamentExceptions::report($e);
            }
        });

        ...
    }

Bug on publish filament component

I got error trim(): Argument #1 ($string) must be of type string, Filament\Support\Enums\IconPosition given when i published filament component with command php artisan vendor:publish filament-views.

I got this error without changes any code on filament-views component. is this possible from this package or filament it self, cause the error is coming at file resources/views/vendor/filament/components/tabs/item.blade.php in e at line 56?

Array to string error

When array exists in the elements of $values, the page errors out with ErrorException(code: 0): Array to string conversion.

Allow for custom model

Hey,

Can you allow for custom model?

I'm using multiple database tenancy so need to modify the model to use the central connection :)

Thanks

Filament v3: Missing info: Register plugin

Hi,

This plugin is missing Filament V3 installation info:

4. Register the plugin for the Filament Panel

public function panel(Panel $panel): Panel
{
    return $panel
        ->plugins([
            \BezhanSalleh\FilamentExceptions\FilamentExceptionsPlugin::make()
        ]);
}

Unsupported operand types: string + int

Description

Steps to reproduce the bug:

Use named bindings in a database query, for example:

DB::select('select * from users where id = :id', bindings: ['id' => 1])

In my case, I have a stored procedure in another Oracle OCI connection that is called in the same manner, using named bindings.

When there is a query error, the package saves the bindings, but within resources/components/query-preview.blade.php, there is a section of code that retrieves the key and adds 1:

...
@foreach ($query['bindings'] as $key => $value)
    <div class="flex px-4 py-2">
        <div class="py-2 font-mono text-gray-500 basis-1/12 dark:text-gray-400">
            {{ $key + 1 }}
        </div>
        <div
            class="px-4 py-2 font-medium text-gray-500 rounded-lg basis-11/12 dark:text-gray-200 bg-gray-950/5 dark:bg-white/5">
            {{ $value }}
        </div>
    </div>
@endforeach
...

Since the key is a string due to the named bindings, this results in an "Unsupported operand types: string + int" error.

Expected behavior:

The component should handle named bindings correctly without throwing an error.

Current behavior:

The application throws an "Unsupported operand types: string + int" error when named bindings are used and the key is a string.

Package version:

"bezhansalleh/filament-exceptions": "^2.1"

Environment:

PHP: 8.2.1
Laravel: 10.48.14
Operating System: WSL with Ubuntu 20.04

Pull Request Suggestion

To fix this issue, I suggest adding a validation to check if the key is an integer before performing the addition. Here is the proposed change:

File: resources/components/query-preview.blade.php

...
@foreach ($query['bindings'] as $key => $value)
    <div class="flex px-4 py-2">
        <div class="py-2 font-mono text-gray-500 basis-1/12 dark:text-gray-400">
            {{ is_int($key) ? ($key + 1) : $key }}
        </div>
        <div
            class="px-4 py-2 font-medium text-gray-500 rounded-lg basis-11/12 dark:text-gray-200 bg-gray-950/5 dark:bg-white/5">
            {{ $value }}
        </div>
    </div>
@endforeach
...

This modification ensures that if the key is an integer, it will be incremented by 1. If it is a string, it will be displayed as-is, preventing the "Unsupported operand types: string + int" error.

Feel free to adapt this to better fit the style and requirements of your bug report and pull request.

Data too long for column 'message' at row 1

Some exception not saved to database because message is too long to save into message column that only has length 255.

Sorting not working

/** Show or hide in navigation/sidebare */
'navigation_enabled' => true,

/** Sort order, if shown. No effect, if navigation_enabled it set to false. */
'navigation_sort' => 10,

Still on top.
Also how do i add this to a navigation group?

Exception messages are not displayed

When exceptions are viewed, all relevant information are displayed except the message

Localization

I've requested PR for localization en

#7

No error record is insert to database

Hey in your latest update there is no error record insert to database. Exception table is always 0.