- How do I install pjedesigns/filament-nested-set-table in a Laravel Filament panel?
- Install it with Composer, register the plugin in your Filament panel provider, and generate or publish the OrderPage for the target resource. Point the page at your Eloquent model and configure the sort column and depth settings. Ensure the model already uses the required nested-set trait, and publish translations if you support non-English locales.
- Which Filament versions does this nested set table plugin support?
- The package targets Filament panels, but the provided notes do not state a formal support matrix or CI matrix. Check the repository composer constraints and release notes before installing. Because the plugin touches Filament table DOM and CSS contracts, pin versions and run visual checks after Filament minor upgrades.
- Does this package work with kalnoy/nestedset or another nested set implementation?
- The plugin depends on a nested-set persistence layer but the provided notes do not name the specific package or trait. Verify the required Composer dependency and model trait in the package documentation or composer.json. Treat the plugin as a presentation layer that consumes your nested-set schema rather than owning it.
- Can I use this as a drop-in replacement for a Filament Table on an existing resource?
- It is described as a drop-in replacement for Table, but version 1.1.0 moves reordering into a dedicated OrderPage surface. For an existing resource, add the OrderPage and point it at the model while keeping your normal list table for browsing. A safe migration is to adopt it one resource at a time and keep the old reorder path available until validated.
- How does drag-and-drop reordering handle concurrent edits or conflicts?
- The provided assessment notes no evident optimistic-locking story, so drag reorder should be treated as a concurrent-write path that may be last-write-wins. Add row locking, updated_at checks, or another serialization strategy if multiple admins reorder the same tree. For business-critical high-concurrency ordering, a drag UI may be the wrong interface regardless of plugin quality.
- What does the Fix Tree action do and is it safe to run in production?
- Fix Tree is a repair operation against the nested-set store and is inherently destructive if the tree is already inconsistent. Gate it behind permissions, run it transactionally where the database driver allows, and audit who runs it. The notes do not confirm whether the package already does this, so verify before enabling it for non-admin roles.
- Is the Undo feature durable across page navigation?
- Undo is surfaced through Filament notifications, so it inherits notification lifecycle semantics. The provided notes specifically ask whether Undo is durable and server-side or scoped to the session or notification. Confirm the undo window and whether it survives navigation before relying on it for recovery.
- Does the OrderPage respect Filament authorization policies and multi-tenancy scoping?
- As a first-class Filament Page, OrderPage should integrate with panel authorization, but the notes list policy enforcement and tenancy scoping as open questions. Confirm that the parent resource update policy is checked and that multi-tenancy scopes apply to the tree query. Test with non-admin roles and multiple tenants before rollout.
- How does the tree behave with large hierarchies and is it lazy loaded?
- The notes ask whether the tree is lazily loaded or fully hydrated into the DOM, and do not state the answer. For large hierarchies, test drag responsiveness and page load time in a real panel. Depth is a declared configuration value with conditional description text, so explicit depth limits can help control the rendered tree.
- What are the alternatives to this package for managing hierarchical Laravel models in Filament?
- Alternatives include building a custom Filament page around your nested-set package, maintaining manual sort_order columns with a reorder form, or using another tree-table plugin. This package fits content-heavy admins such as categories, menus, and page hierarchies. It is a poorer fit for high-concurrency, business-critical ordering where drag-and-drop is not the right workflow.