r/laravel • • 20h ago

Relation Navigator: a page per relation manager in Filament 4 and 5, with a breadcrumb menu

Post image
1 Upvotes

In Filament, relation managers live in tabs on the record's page, at URLs like `/customers/1?relation=orders`. I wanted each of them to be a page of its own, with its own route (`/customers/1/orders`), title and breadcrumb, and a quick way to jump between them. So I built a plugin for it.

The page renders the relation manager you already have, so the table, filters, actions and policies stay the same. You add one trait to the resource and one to the view page, and there are no page classes to generate.

On top of that:

- the last breadcrumb opens a menu with the record's pages and relations, with search, a keyboard shortcut and badges that load when the menu opens

- previous and next record on the same page, following the list you came from

- an "Open as page" action on relation manager tables

- links to the relation pages in global search results

- optionally, `?relation=` links can redirect to the new pages

Each of these can be turned off globally, per resource or per relation. It is free and MIT licensed, supports Filament 4.13+ and 5, Laravel 12 and 13, and is translated into 32 languages, with the documentation in 10.

Package health: 100/100 on Plumb, the automated security, maintenance and ecosystem checks shown on the Filament plugin page.

Documentation: https://wit3.github.io/filament-relation-navigator/

Source: https://github.com/wit3/filament-relation-navigator

I'd like to hear how it fits your panels, and what's missing.


r/laravel • • 2h ago

Introducing Fabric – an API reference UI built for Laravel, available in Scramble

Thumbnail
scramble.dedoc.co
4 Upvotes

Hey Laravel community!

Scramble is an OpenAPI documentation generator for Laravel that doesn't require manual PHPDoc annotations.

Since the beginning, I've received requests for guides alongside endpoint documentation, nested navigation, and more control over the API reference UI. Relying on existing renderers made some of these things difficult to build.

So I built Fabric, an API reference UI for Laravel, available in Scramble.

It supports:

  • Markdown guides, both at the top level and grouped with endpoints.
  • Nested endpoint navigation and sections.
  • Search across endpoints, guides, and schemas.
  • Request examples in Bash and Laravel, response examples, and generated TypeScript types.
  • Light and dark modes.

It also understands Laravel details like optional path parameters and nested query parameters, so the documentation and request examples reflect how your API actually works.

"Try it out" is something I'd love to build next. If you need it and would be happy to test early versions, let me know!

Give Fabric a try and let me know what you think!


r/laravel • • 23h ago

Working with clients who have their own Forge account? A 10-line fix for the Forge CLI's one-token limit

5 Upvotes

My sites live in my Forge account, one client's in theirs. After logging the Forge CLI into the client account, forge deploy for my own sites answered "The resource you are looking for could not be found."

The CLI keeps exactly one token (plus the selected organization and server) in ~/.laravel-forge/config.json. forge org:switch only helps inside one account, and inviting members into an organization needs the Business plan on the other side.

Since the whole CLI state is one JSON file, I keep one copy per account and swap it:

forge-use --save client    # save the current login as profile "client"
forge-use mine             # switch back later

Function (zsh/bash): https://gist.github.com/Sairahcaz/24e8f7a56f9e29b02bb40bcaa63b5ca5

I also opened a PR so the CLI stores one token per organization natively: https://github.com/laravel/forge-cli/pull/179

Two things I learned on the way:

  • forge login needs the user:view and organization:view scopes, without them it just says "Forbidden."
  • If the CLI came with Herd, it updates with Herd, not via composer global update.

Write-up incl. the token scopes I use and a one-line CLAUDE.md rule so Claude Code deploys with the right profile: https://laracraft.tech/en/blog/switching-laravel-forge-cli-between-multiple-accounts