Weave Code
Tomato Relation Manager Laravel Package
tomatophp/tomato-relation-manager
A Laravel package for managing Eloquent model relationships with ease. Browse, attach, detach, and edit related records through a clean, configurable interface, simplifying relation handling in your admin panels and applications.
Relation Manager For Laravel TomatoPHP Splade
Frequently asked questions about Tomato Relation Manager
- What is tomatophp/tomato-relation-manager used for?
- It is a Laravel package for managing Eloquent model relationships inside TomatoPHP Splade admin interfaces. It lets developers browse, attach, detach, and edit related records through a configurable interface. It is most useful when an admin panel needs relationship management without building custom CRUD screens.
- How do I install tomatophp/tomato-relation-manager?
- Install it with Composer using composer require tomatophp/tomato-relation-manager, then follow the package README for any publish, configuration, or migration steps. Because it is built for TomatoPHP Splade, make sure that stack is already configured in your Laravel application. Check that package discovery registers the service provider correctly after installation.
- Which Laravel versions does tomato-relation-manager support?
- The supported Laravel versions are defined by the package's Composer constraints, so check composer.json or the README before installing. If your application uses a newer or older Laravel release, confirm compatibility and test the package in staging. Do not assume compatibility with every Laravel version without verifying the dependency requirements.
- How do I configure which relationships appear in the manager?
- Configuration depends on how you register the relation manager within your TomatoPHP Splade resource or admin setup. Use the package's documented configuration options to define the model, relationship, and displayed fields. Consult the README for the exact keys and examples before customizing the interface.
- Can I attach and detach related records without custom code?
- Yes, the package provides interface actions for browsing, attaching, detaching, and editing related records, reducing the need for custom CRUD code. You should still use Laravel authorization policies and validation to control who can perform those actions. Test the workflows with your actual models before relying on them in production.
- Does it work with hasMany, belongsToMany, and morph relationships?
- The package is built around managing Eloquent relationships, but the exact relation types supported should be verified in the README. Test your specific hasMany, belongsToMany, morphToMany, or other relationship types in staging before using them in production. If a relation type is not explicitly documented, confirm behavior with a small test case.
- Is tomato-relation-manager suitable for production admin panels?
- It can be suitable for TomatoPHP Splade admin panels, but treat it like any admin dependency and review authorization, validation, and database safety. Test attach, detach, and edit flows in staging and ensure backups and access policies are in place. Also review recent releases and open issues before deploying it to production.
- How should I test relation management in my Laravel application?
- Write feature tests that exercise the manager's attach, detach, and edit flows against test models and assert the expected database changes. Use Laravel's testing helpers with a dedicated test database, and cover authorization and validation paths as well. Testing these flows helps catch relationship or permission issues before they reach production.
- What are alternatives to Tomato Relation Manager?
- Alternatives include Filament relation managers, Laravel Nova relationships, Backpack CRUD, or custom Livewire components. Tomato Relation Manager makes the most sense if you already use TomatoPHP and Splade in your admin stack. Otherwise, compare its features and maintenance status with the admin tooling your team already knows.
- How is tomato-relation-manager maintained and where do I report issues?
- Maintenance happens in the public GitHub repository, so check recent commits, releases, and open issues before adopting the package. Report bugs or feature requests through the repository's issue tracker and review the license and contribution guidance. For production use, also confirm that the package is actively compatible with your Laravel version.
Weaver
How can I help you explore Laravel packages today?