Weave Code
Hades Laravel Package
lara-zeus/hades
Hades is part of the Lara Zeus family of Laravel packages, adding a focused, config-driven tool to your Filament admin panel. Install it with Composer, publish the config, and drop it into your existing resources with minimal setup.
Hades let users to save forms as a draft
Frequently asked questions about Hades
- What is lara-zeus/hades and what does it actually do?
- Hades is a Laravel package from the Lara Zeus family that lets users save form entries as drafts instead of losing partially completed work. It ships as a plugin for Filament admin panels and is driven by published configuration rather than hardcoded behaviour. You install it with Composer, register it on a panel, and attach it to your existing resources with minimal setup.
- How do I install lara-zeus/hades in a Laravel application?
- Run composer require lara-zeus/hades, publish the package config, migrations, and assets with the vendor:publish command, then register the plugin on your Filament panel provider and run php artisan migrate. Laravel package discovery registers the service provider automatically, so no manual provider entry is needed. Confirm your Filament major version matches the package major version first, because 3.x targets Filament v5.
- Does lara-zeus/hades 3.0 require Filament v5?
- Release 3.0.0 rebases the package on Filament v5, so 3.x is built for panels already on v5 or greenfield projects. The release notes are only two bullets and do not clarify whether the Composer constraint is hard-exclusive or still tolerant of Filament v3 and v4. Check the require block in the package composer.json before assuming anything.
- Can I use lara-zeus/hades with Filament v3 or v4?
- Not on 3.x, because the package major version is now coupled to the Filament major version. If your panels still run Filament v3 or v4, stay on the 2.x line and pin it explicitly as ^2.0 in composer.json with a committed lockfile. Adopting 3.x is effectively gated behind a full Filament upgrade project that is much larger than the package update itself.
- How do I register the Hades plugin on a Filament panel provider?
- Add the plugin class to the plugin list inside your panel provider and verify the panel still boots, then clear cached config and components with php artisan optimize:clear. The exact class name and method signature should be confirmed against the README for the specific major version you install, since the 3.0.0 notes do not enumerate API or registration changes. If registration fails after a version bump, treat it as a breaking change rather than a misconfiguration.
- What PHP and Laravel versions does lara-zeus/hades 3.0 support?
- The 3.0.0 release notes only mention the Filament v5 rebase and a documentation restructure, with no stated PHP or Laravel minimums. Read the require block in the package composer.json or the Packagist listing and compare it against your pinned PHP and Laravel baseline. If the constraints conflict with your platform baseline, 3.x is not a stack fit yet regardless of how well it fits your panels.
- Is upgrading lara-zeus/hades from 2.x to 3.x safe?
- Not without review, because 3.0.0 ships as a semver major with no documented list of changed public APIs, renamed config keys, altered namespaces, or added and removed migrations. The accompanying docs restructure can also break deep links, anchors, and internal runbooks that reference specific documentation pages. Diff your overridden config values and published assets against a scratch install of 3.x before touching production branches.
- Is the lara-zeus/hades 2.x branch still maintained?
- This is the largest operational unknown around the package. If 2.x is effectively frozen, applications that cannot move to Filament v5 are stranded on 2.0.1 with no bugfix or security path. Confirm with the maintainers whether 2.x still receives bugfixes, whether it receives security fixes, and for how long, before committing to either line.
- How should I test or evaluate lara-zeus/hades before adopting it?
- Spin up a throwaway Laravel app on Filament v5, install the package, publish config and migrations, register the plugin, and confirm draft saving behaves correctly against a representative resource with real form state. That evaluation is low effort and answers most questions about fit. Production adoption in an existing codebase is high effort because it depends on completing the Filament major migration first.
- What are the alternatives to lara-zeus/hades for saving Filament form drafts?
- You can build a drafts table plus a form state observer yourself, or lean on Filament's own form state handling and autosave behaviour, but Hades packages the workflow as a config-driven plugin. The trade-off is a single-vendor dependency whose release cadence is set by every Filament major, outside your control. Weigh that maintenance treadmill against the cost of owning a small in-house draft layer.
Weaver
How can I help you explore Laravel packages today?