Filament Gaze Laravel Package

Getting Started

Start by installing the package per its README and locating the GazeColumn class and the table/query integration point where columns are declared. The first thing to verify after upgrading to 2.2.1 is that GazeColumn::make()->identifier('any-order') is supported in your installed version.

Minimal first use case:

use GazeColumn;

GazeColumn::make()->identifier('any-order');

Use this when a column needs an explicit identifier rather than relying on the default column name/key. Look first at the package README, the GazeColumn source, and any tests covering identifier() to confirm how the identifier is consumed by sorting, filtering, or request handling.

Implementation Patterns

• Declare columns in one place, such as a dedicated method, config file, or table definition class, and chain identifier() there.
• Use identifier() to decouple the public request/UI key from the underlying database column or display label.
• For the new 2.2.1 behavior, use GazeColumn::make()->identifier('any-order') when the column should be addressed by the any-order identifier in the package’s column map.
• Keep identifiers stable and centralized, for example as class constants, so controllers, form requests, and tests do not drift.
• Validate incoming identifiers at the Laravel boundary with a FormRequest or explicit allow-list before passing them into package column resolution.
• Add a feature test that asserts the column identifier is present in the generated table/column payload:

$columns = $this->get('/report')
    ->assertOk()
    ->viewData('columns');

$this->assertSame('any-order', $columns[0]->identifier());

• If the package serializes columns to JSON for a frontend table, confirm the identifier is what the frontend sends back in sort/filter requests.

Gotchas and Tips

• 2.2.1 appears additive and non-breaking: it adds support for identifier('any-order') on GazeColumn::make(). There is no indicated migration or deprecation.
• Do not assume any-order has special ordering semantics unless the package docs say so. The release note only states identifier support; verify whether it is a literal identifier or a reserved keyword.
• Check whether identifiers must be unique. If multiple columns use identifier('any-order'), confirm the package resolves them deterministically.
• Debug by inspecting the column definition or serialized output rather than only the rendered view. Confirm the identifier survives any column transformation, caching, or resource layer.
• Clear Laravel config/view caches after upgrading if column definitions are cached.
• If the package exposes macros or subclassing, keep custom identifier logic in a package-specific extension point rather than scattering identifier() calls across controllers.