Fixing Late Static Binding Issues in Filament Resources

When developing with Filament, you might encounter issues with PHP's late static binding, especially when working with resources. A recent update to the platform project addressed such a problem, improving the way queries are handled within resource classes.

The issue arose from directly calling Resource::getEloquentQuery(). This approach breaks PHP's late static binding, causing static::class to resolve to Resource instead of the intended resource class (e.g., RateResource). This, in turn, could lead to errors like "Class App\Models\ not found" if the resource relies on a specific model.

The Solution

Instead of using Resource::getEloquentQuery(), the fix involves calling the model's query method directly. In the case of the Rate resource, the change was to use Rate::query() instead. This ensures that the query is properly scoped to the Rate model, as rates are global and do not require additional scoping.

Here's an example illustrating the concept:

// Before (incorrect)
// $query = Resource::getEloquentQuery();

// After (correct)
$query = Rate::query();

// Applying any filters to the query
$records = $query->paginate(15);

By calling Rate::query(), the query operates directly on the Rate model, avoiding the late static binding issue and ensuring that the correct model is used.

The Takeaway

When working with Filament resources, always prefer calling the model's query() method directly instead of relying on Resource::getEloquentQuery(). This approach prevents potential issues with late static binding and ensures that your queries are correctly scoped to the intended model, leading to more robust and maintainable code. This is especially important when dealing with global resources that don't need additional scoping. When in doubt, call the Model.