Download the PHP package harvirsidhu/filament-action-overflow without Composer

Filament Action Overflow

Turn a flat list of Filament actions into a few primary buttons + a tidy "More" dropdown — automatically.

You declare every action in one list. The package decides which ones sit out front and which get tucked under More, so crowded action rows stop wrapping and your UI stays clean.

Works anywhere Filament accepts an action array — page headers, table actions, record actions, bulk actions, widgets.

Contents

• Why this package
• Requirements
• Installation
• Quick start (30 seconds)
• The two ways to use it
• How it decides what overflows — the mental model
• Recipes
  • Choose how many primary actions
  • Style the More trigger
  • Put More on the left (and RTL)
  • Sections inside the menu (dividers)
  • Hidden, invisible & unauthorized actions
  • Button vs. link appearance
  • Set defaults globally
• API reference
• Under the hood
• FAQ
• License

Why this package

• One line to adopt. Append ->withOverflow() to any ActionGroup.
• Smart by default. Nothing to overflow → no More button. One leftover action → shown inline, not buried. Two or more → grouped under More.
• Section-aware. Filament's ->dropdown(false) divider groups flow into the menu as real, separated sections.
• Visibility-aware. ->hidden(), ->visible(false), and (opt-in) ->authorize(...) are all honored before anything is composed, so hidden actions never leak into More.
• Direction-aware. Position More at the start or end; under RTL it flips correctly with zero extra config.
• Filament 4 & 5. A single compatibility layer keeps one codebase working across both.

Requirements

Installation

That's it — the package auto-registers and works with zero configuration.

Only publish the config if you want to change the defaults globally:

Quick start (30 seconds)

Build an ActionGroup exactly as you normally would, then chain ->withOverflow() and return the result:

withOverflow(int $primary = 1) is terminal: it returns the finished array<Action|ActionGroup>, ready to hand straight back from getHeaderActions(), getTableActions(), getRecordActions(), getBulkActions(), and so on.

By default, the primary actions and the More trigger are rendered as buttons, so you get a row of matching buttons without sprinkling ->button() everywhere.

The two ways to use it

There are exactly two entry points. Pick based on whether you need to customize the More button.

Macro — shortest path:

Facade — when you want to change the trigger or behavior:

Both produce the same kind of output — the macro is just sugar over the facade with primaryCount set.

How it decides what overflows

The whole package is one deterministic pipeline. Understanding it means you can always predict the output.

1. It filters first. Hidden, invisible, and (if you opt in) unauthorized actions are removed before anything else — including those nested inside divider sections. Only available actions are ever counted or placed.

2. It fills primary slots left-to-right. Walking your list in order, it promotes actions to the front until primaryCount is reached (default 1). Everything after that overflows. Order is preserved — the list order is the priority order.

3. It applies the count rule to whatever is left:

4. It positions the More control at the end (default) or start of the row — see Put More on the left.

That's the entire model. Everything below is just configuring these steps.

Recipes

Choose how many primary actions

primaryCount controls how many actions stay out front. The rest overflow.

primaryCount(0) is valid and pushes everything into More. Negative values throw an InvalidArgumentException.

Style the More trigger

Only available via the facade (the macro intentionally keeps its surface tiny):

• icon() accepts a plain string ('heroicon-m-bars-3'), a backed enum, or a Filament icon enum like Heroicon::EllipsisVertical.
• hiddenLabel() is honored only on Filament versions that support hidden labels; on older versions it's silently ignored rather than crashing.

Put More on the left (and RTL)

By default the More control sits after the primary actions. Use MorePosition::Start to put it first:

This is the right answer to "how do I support RTL?" — there's nothing extra to do. The package only reorders the array, and Filament renders that array in the reading direction. So Start means the reading start: it lands on the left in LTR and automatically flips to the right under RTL. Use Start/End (logical) rather than thinking left/right (physical), and direction handling is free.

The position applies to the flattened single-action case too, not just the grouped More trigger.

Sections inside the menu (dividers)

A dropdown(false) group nested inside an ActionGroup is Filament's idiom for "render these as a separated section." This package treats those as first-class and carries them into the More menu:

How dividers behave — predictable and lossless:

• A divider never consumes a primary slot — its children do. With primaryCount(2) and a leading divider whose first child is submit, submit is promoted to primary; the divider's remaining children stay grouped in overflow.
• Dividers never appear among the side-by-side primary buttons — separators only make sense inside a dropdown.
• A divider at the very top of the menu is unwrapped, so you don't get an orphan separator line above the first item.
• Trailing and adjacent dividers are preserved as distinct sections — exactly how Filament renders multiple dropdown(false) groups natively.
• Unavailable children are dropped from a divider; if every child is gone, the whole divider disappears.

Hidden, invisible & unauthorized actions

Hidden and invisible actions are filtered automatically — they're gone before composition, so they can't sneak into More:

Authorization filtering is opt-in, because Filament's renderer already disables unauthorized actions visually. Enable it when you'd rather drop them entirely:

Button vs. link appearance

By default, primary actions and the More trigger are promoted to button view so the row looks uniform. To leave each action's own render style untouched, opt out:

button(false) is opt-out only — it stops the composer from adding ->button(). An action you already styled with ->button() keeps its button view regardless.

Set defaults globally

Prefer to configure once instead of per-call? Publish the config and edit the defaults — every withOverflow() / ActionOverflow::make() call inherits them (and per-call methods still override per call):

API reference

ActionGroup::withOverflow() macro

Terminal. Composes the group's actions with the given primary count, using config defaults for everything else. Returns the finished action array.

ActionOverflow fluent API

Every method returns $this for chaining; toActions() ends the chain and returns the array.

MorePosition enum

Harvirsidhu\FilamentActionOverflow\Enums\MorePosition

Config keys (config/action-overflow.php)

Defaults are stored as strings (not Filament enum constants) so the published file loads cleanly on both Filament 4 and 5. You may still pass enums at the call site.

Under the hood

For the curious, toActions() runs a fixed five-stage pipeline:

1. Filter — remove hidden / invisible / (opt-in) unauthorized actions, recursing one level into divider groups and dropping any divider left empty.
2. Partition — walk left-to-right, taking primaryCount real actions into primary; a divider contributes its children toward that count and re-wraps any leftovers as a divider in overflow.
3. Promote — if button is on, call ->button() on the primary actions.
4. Sanitize — unwrap a leading divider in the overflow so there's no orphan separator at the top of the menu.
5. Assemble — count the available overflow actions and apply the 0 / 1 / 2+ rule, then place the result at the start or end per morePosition.

The package never renders HTML — it only restructures the action array and hands it back to Filament, which means it composes naturally with everything Filament already does (theming, RTL, authorization display, etc.).

FAQ

Why didn't a "More" button appear? You have one or zero overflow actions. A single leftover is shown inline by design; More appears only with two or more.

Why is one of my overflow actions a plain button instead of being in the dropdown? Same rule — when exactly one action overflows, it's surfaced inline rather than hidden behind a dropdown for a single item.

Do I need to do anything for RTL? No. Use morePosition(MorePosition::Start) for "leading side"; it flips automatically with the layout direction. See Put More on the left.

Can I use it outside page headers? Yes — the output is just an action array, valid anywhere Filament accepts one (tables, records, bulk actions, widgets).

An action's visibility depends on the record — is that respected? Yes. Filtering calls the same isHidden() / isVisible() / isAuthorized() your action defines, so record-aware closures are honored.

Testing

Changelog

See CHANGELOG for release notes.

Credits

• harvirsidhu

License

MIT — see LICENSE.