- What is niladam/quick-links used for in Laravel?
- niladam/quick-links is a small Filament plugin that adds configurable shortcut links to Filament table headers, so operators can open related resources or files directly in PHPStorm. It is a presentation-layer package with no migrations, models, jobs, or persistence of its own. It fits admin panels and dashboards where quick outbound links belong next to a resource table.
- How do I install niladam/quick-links with Composer?
- Install it with Composer using composer require niladam/quick-links, then register the package's Filament plugin in your panel provider. Define links through the builder API, such as buildResourceLinks(), buildFileLinks(), and build(). Publishing the Blade view is optional and only needed if you want to change the rendered markup.
- Which Filament and PHP versions does quick-links support?
- Quick-links v2 supports Filament tables v3, v4, and v5 concurrently and requires PHP 8.2 or newer. Composer enforces both constraints through the package dependencies, so incompatible PHP or Filament versions fail at install time rather than at runtime. Filament v2 and PHP 8.1 are not supported by v2.
- Why are my quick links not showing in the Filament table header?
- In v2, links render through the tables::header.after hook, and Filament hides that header container when a table has no heading, description, header actions, search, filters, or column manager. On such bare tables the links silently do not render. Add one of those header elements or publish and customize the view if you need links on every table.
- How do I publish and customize the quick-links Blade view?
- Run php artisan vendor:publish --tag=quick-links-views to publish the package Blade view into your application. You can then edit the markup to match your design system instead of forking the package. Keep in mind that published views become your maintenance responsibility when the package updates.
- What changed in quick-links v2 for build(), buildResourceLinks(), and buildFileLinks()?
- In v2, buildResourceLinks() and buildFileLinks() return structured arrays with url and label keys instead of HTML strings, and build() returns a View or Htmlable instead of HtmlString. Any code that echoed, concatenated, or regex-tested those return values must be updated. Treating the new array or View as a string can fail or produce unexpected output.
- How does disableIf() behave in quick-links v2?
- In v2, the disableIf() closure is evaluated per render, and returning true now disables the link. In v1 the result was applied inverted and evaluated once at registration, so workarounds written for the old behavior will now do the opposite. Audit every disableIf() call after upgrading.
- How do I migrate from quick-links v1 to v2 safely?
- Start by inventorying plugin registrations, disableIf() calls, and any consumers of build() output. Raise your PHP runtime to 8.2 or newer, rewrite string consumers to handle arrays and View objects, and verify the new disableIf() semantics. Then test tables that may be bare, because links moved to the header hook and may not render there.
- Can I use quick-links in production or on Laravel apps running PHP 8.1?
- The package is low-risk at runtime because it adds no database, queue, or cache dependencies and only decorates the Filament render layer. The main production concerns are the PHP 8.2 floor and the v2 breaking changes around return types and disableIf(). Pin a tested version and run your Filament panel tests after upgrading. Laravel apps on PHP 8.1 cannot use v2.
- Is quick-links a good alternative to custom Filament header actions?
- Quick-links is a good fit when you want configurable links colocated with Filament resource tables without writing custom header actions. For more complex workflows, native Filament header actions or a custom Blade partial may offer more control. The package is intentionally narrow, so evaluate it as presentation-layer decoration rather than core application logic.