fix: support standalone Filament usage without panel dependency#86
Merged
ManukMinasyan merged 5 commits into4.xfrom Mar 1, 2026
Merged
fix: support standalone Filament usage without panel dependency#86ManukMinasyan merged 5 commits into4.xfrom
ManukMinasyan merged 5 commits into4.xfrom
Conversation
Replace `filament/filament` (full panel) requirement with individual sub-packages (actions, forms, schemas, support, tables). This allows the package to be installed in projects using standalone Filament components without triggering NoDefaultPanelSetException. Panel-specific classes (BoardPage, BoardResourcePage, FlowforgePlugin) remain available but are only autoloaded when explicitly used. Closes #84
There was a problem hiding this comment.
Pull request overview
Updates Flowforge’s dependency setup to allow installing and using the package with standalone Filament components (Forms/Tables/etc.) without forcing the full Filament Panel Builder, while documenting which classes still require a panel context.
Changes:
- Replaces the hard
filament/filamentruntime dependency with individual Filament sub-packages needed for standalone operation. - Moves
filament/filamenttorequire-devand adds it tosuggestfor panel integrations. - Adds docblocks to panel-specific classes (
FlowforgePlugin,BoardPage,BoardResourcePage) clarifying the panel requirement and pointing standalone users toInteractsWithBoard.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
composer.json |
Splits Filament dependencies into sub-packages, adds suggest, and moves filament/filament to dev-only. |
src/FlowforgePlugin.php |
Documents that the plugin is panel-specific and points to standalone usage via InteractsWithBoard. |
src/BoardPage.php |
Notes the panel dependency for Filament Page integration and points to standalone trait usage. |
src/BoardResourcePage.php |
Notes the panel dependency for Filament Resource Page integration and points to standalone trait usage. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Adds a StandaloneTestCase and TestStandaloneBoard fixture that verify board rendering, card movement, and pagination work without a Filament panel registered. This directly tests the fix for #84. Moves ArchTest into Feature/ directory to support separate Pest test case bindings per directory.
- sort composer.json require entries (ext-bcmath first) - add strict_types to FlowforgePlugin, remove unused import and dead code - clean up standalone test names (remove redundant suffixes)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
filament/filament(full Panel Builder) inrequirewith individual sub-packages (filament/actions,filament/forms,filament/schemas,filament/support,filament/tables)filament/filamenttorequire-dev(for tests) andsuggest(for panel users)BoardPage,BoardResourcePage,FlowforgePlugin) noting the panel requirement and pointing toInteractsWithBoardfor standalone useCloses #84
Why
Installing FlowForge in a project using standalone Filament components (only
filament/forms+filament/tables, no admin panel) throwsNoDefaultPanelSetExceptionbecausecomposer.jsonrequires the fullfilament/filamentpackage, which enforces panel registration.The core board functionality (
InteractsWithBoard,Board,Column, cards, drag-and-drop) only usesfilament/actions,filament/forms,filament/support,filament/schemas, andfilament/tables-- no panel required. Panel-specific classes (BoardPage,BoardResourcePage,FlowforgePlugin) are only autoloaded via PSR-4 when explicitly referenced, so standalone users never trigger them.Test plan
filament/filamentis NOT pulled intocomposer.lockfor production installsNoDefaultPanelSetException