Weave Code
Fixtures Plugin Laravel Package
monofony/fixtures-plugin
A Monofony plugin that adds fixtures support, letting you load demo data and sample content into your application for development and testing. Simplifies seeding entities so you can bootstrap a working environment quickly and reliably.
At a glance
Frequently asked questions about Fixtures Plugin
- Is monofony/fixtures-plugin compatible with Laravel?
- No. monofony/fixtures-plugin is a Symfony bundle scoped to Monofony, which is a Sylius-derived e-commerce framework. It integrates through Symfony bundle registration, the service container, Doctrine ORM mappings, and Sylius/Alice fixture conventions, none of which map to Laravel service providers, Eloquent, factories, or Artisan. For Laravel, use native seeders and model factories.
- How do I install monofony/fixtures-plugin in a Monofony application?
- Install it with composer require monofony/fixtures-plugin inside an existing Monofony application. Register the bundle in config/bundles.php, define your fixture YAML or fixture classes, and invoke the console loader. The main gate is whether the package's PHP, Symfony, Monofony, and Sylius constraints resolve against your target stack.
- Does monofony/fixtures-plugin support Laravel 10 or Laravel 11?
- It has no Laravel version support because it is not a Laravel package. Its compatibility matrix is built around PHP, Symfony, Monofony, and Sylius constraints. Do not expect Composer resolution against Laravel 10 or Laravel 11; use Laravel's own seeding tools instead.
- How do I load fixtures with this plugin?
- The plugin provides Symfony console commands to load or purge fixtures on demand. Fixtures are defined as reusable classes or YAML and can be grouped into ordered, dependency-aware suites. Because command names have drifted between sylius:fixtures:load and monofony:fixtures:load across versions, confirm the exact name with bin/console list before scripting it.
- Can monofony/fixtures-plugin be used in production?
- Treat it as development, demo, and test or CI tooling, not a production runtime dependency. The security surface is minimal because fixture loading is not a production path, but availability and longevity risks remain. Keep it out of production deployment workflows.
- What are the Laravel alternatives for seeding demo data?
- Use Laravel's native db:seed command, model factories, and Faker for deterministic, environment-partitioned seed data. Packages such as orangehill/iseed can help generate seeders from existing data. There is no in-place migration from this Monofony plugin to Laravel, only a conceptual port.
- Is monofony/fixtures-plugin actively maintained?
- The package shows very low adoption, with 1 star, 0 dependents, and a composite score of 0.005 in the assessment. Assume near-zero upstream responsiveness and expect version drift against current Symfony LTS and PHP releases. The MIT license is the main mitigant because it allows a fork or vendoring if you must keep it alive.
- How does dependency-aware fixture ordering work?
- Fixtures are declared as fixture classes or YAML and organized into suites with dependency-aware, ordered execution. You can load or purge them on demand through console commands. Define dependencies in the fixture configuration so reference data and entities are seeded in the correct sequence.
- What happens when Doctrine migrations change Monofony entity fields?
- The fixtures can be schema-coupled to specific Monofony entities, so Doctrine migrations that rename or drop fields can break them. The assessment does not identify a test suite proving end-to-end loading, so validate fixtures after schema changes. Add your own smoke test that runs the loader against a disposable database.
- What version constraints and console command names should I verify?
- Check composer.json for exact PHP, Symfony, Monofony, and Sylius constraints before committing engineering time. Also verify the last commit and release, whether a maintained branch exists per Monofony major, and the exact console command namespace. Run bin/console list to resolve the sylius:fixtures:load versus monofony:fixtures:load drift.
Weaver
How can I help you explore Laravel packages today?