Easy way to check the current page inside resource class

[migueliriano]

Sometimes we have a different behavior when you are in an edit or creating form using a resource, so for that, we need to identify what is the page that is active at the moment.

For example, if we create a Property resource with the following pages:

• CreateProperty
• EditProperty
• ListProperties

I want to check if the current page is the EditProperty inside the PropertyResource class I have to do the next:

$isEditPage = Route::currentRouteName() === Pages\EditProperty::getRouteName();

I propose to have a helper method inside Filament\Resources\Pages\Page class that is extended for all the pages that check if it's the current page:

This is the code that can be inside the Filament\Resources\Pages\Page class:

public static function isCurrentPage() : bool
{
   return Route::currentRouteName() === static::getRouteName();
}

This is how to use it:

Pages\CreateProperty::isCurrentPage(); // return boolean
Pages\EditProperty::isCurrentPage(); // return boolean
Pages\ListProperties::isCurrentPage(); // return boolean

Example use in real life: In this case, I want to have the Wizard component skippable only on the edit page:

$form ->schema([
      Forms\Components\Wizard::make([...])->skippable(Pages\EditProperty::isCurrentPage())
 ]);

[VictorPennington]

Hi,

If you are working from a resource or from a relation manager, why not use Utilities Injections to achieve what you're trying to do, in this case by Injecting the current operation?

You then could do something like:

use Filament\Forms\Form;

class YourResource extends Resource
{
protected static ?string $model = YourModel::class;

public static function form(Form $form): Form
return $form ->schema([
     Forms\Components\TextInput::make('yourField')
                    ->hint(fn($operation) => "This is a ". $operation . " operation") // you can even inject multiple utilities
 ]);
}

And the result:

Check the documentation below, they are really powerful

https://filamentphp.com/docs/3.x/forms/advanced#injecting-the-current-form-operation
By the way, how do you make your code here colorful?

[migueliriano]

@VictorPennington - Thank you for that approach, I still see it as a workaround because we have to access the operation and do the logic manually, instead of having a helper that does that for us.

Anyway, this can be an alternative solution, thank you for that.

Related to the code color, just create a code block as you did above and add php at the beginning.

Example:

```php

PHP Code

```

That can work for any other language like css js etc.

[BerendSpigt]

I was looking for a way to only show relations on the view page and not on the edit page. I did not find a "Filament" way (maybe there is), but luckily i stumbled on this post. I had to use getRouteName('admin')) because I use multiple panels.

So this is my code in the UserResource:

    use App\Filament\Admin\Resources\UserResource\Pages;
    public static function getRelations(): array
    {
        if (Route::currentRouteName() !== Pages\EditUser::getRouteName('admin')) {
            return [
                MembershipsRelationManager::class,
            ];
        }
        return [];
    }

I don't think the suggested $operation injection is available here, so I think the the proposed helper function would be a useful addition.

[migueliriano]

@danharrin - What do you think about this? It looks like this can be a potentially useful addition, please let me know if we can move forward and start working on the PR (I can work on that).

[danharrin]

Already achievable using ->skippable(fn (string $operation) => $operation === 'edit') or ->skippable(fn ($livewire) => $livewire instanceof EditProperty) so no, sorry not interested

[migueliriano]

Are you able to use the same approach when you don't have access to the $operation injection? for example in this case on getRelations: #10042 (comment)

[danharrin]

canViewForRecord() on the relation manager controls visibility based on $pageClass

[BerendSpigt]

Ok, I now put the following code in canViewForRecord() in the RelationManager, and this works perfectly.

    public static function canViewForRecord(Model $ownerRecord, string $pageClass): bool
    {
        return class_basename($pageClass) === 'ViewUser';
    }

Thanks for pointing in the right direction, feels better to use the Filament way.