Weave Code
Seed Batch Bundle Laravel Package
libre-informatique/seed-batch-bundle
A Symfony/Sylius bundle that adds configurable batch actions to admin grids, letting editors select multiple resources and run bulk operations directly from the grid. It provides reusable batch action services and UI controls to streamline repetitive admin workflows.
[DEPRECATED] Bundle for seed batches management
Frequently asked questions about Seed Batch Bundle
- Can I install libre-informatique/seed-batch-bundle in a Laravel application?
- No. It is a Symfony bundle, not a Laravel package: it ships no Illuminate service provider, no package auto-discovery entry, and no artisan publish path. Composer may download it, but nothing in Laravel will register its services or grid controls. Treat it as zero fit as a dependency in a Laravel codebase.
- What does seed-batch-bundle actually do?
- It adds configurable batch actions to Symfony and Sylius admin grids, letting an editor select multiple rows and run a bulk operation directly from the grid. The work is packaged as reusable batch action services plus the UI controls that render them. The purpose is to shorten repetitive admin workflows, not to supply a seed domain of its own.
- Which Laravel and PHP versions does this package support?
- There is no Laravel support at all: no version constraint, no test matrix, and no service provider targets Laravel. The declared constraints cover PHP, Symfony, and Doctrine, and even those are unverified because the repository has one star and no CI signal. Read composer.json first to see whether those constraints resolve against your lockfile before booking a spike.
- Is libre-informatique/seed-batch-bundle still maintained?
- No. The package description marks it as deprecated, which usually means the code was folded into a larger vendor application and the standalone distribution is no longer the supported path. Expect no patches, no framework-major compatibility work, and no security response. Plan for it as a read-only reference rather than a dependency.
- What license is libre-informatique/seed-batch-bundle released under?
- The repository reports NOASSERTION, meaning no recognized SPDX license is declared. Until the LICENSE file is reviewed and cleared, treat the code as all rights reserved. That blocks copying, forking, and vendoring, so resolve it before any engineer touches the source.
- Can I fork or vendor this bundle into my Laravel project?
- Not without a legal review first, because the license is undeclared and the default position is all rights reserved. Even if the license clears, a fork buys you little: the bundle is deprecated and leans on Symfony and Doctrine conventions you would have to emulate on Laravel. A native reimplementation is usually cheaper than maintaining a port nobody scoped.
- How do I implement bulk batch actions in Laravel instead?
- Reimplement natively: Eloquent models and migrations for the batch records, form requests and policies for authorization, and queued jobs for the bulk operation so large selections do not time out. Chunk the selected ids, dispatch per chunk, and surface progress and failures back to the grid. Filament, Nova, or a small Livewire component can provide the multi-select UI.
- What are the Laravel alternatives to this Symfony bundle?
- For the UI, Filament bulk actions and Laravel Nova actions handle multi-select operations out of the box, and a custom Livewire component works if you use neither. For the backend, a queued job with chunked ids and a status column replaces the bundle's batch action services. None of them supply the seed domain model, which you still have to define yourself.
- What seed batch fields can I reuse from this bundle in Laravel?
- The Doctrine mappings and configuration tree describe a compact seed batch: variety, lot identity, producer or multiplier, generation level, quantity, and quality or certification status. The DependencyInjection configuration tree is the most compact statement of which of those vary per deployment. Port them into an ER diagram, field dictionary, and enumerations, then implement them with Eloquent migrations, policies, and factories.
- Does the bundle ship migrations, fixtures, or tests I can reuse?
- Bundles of this shape normally assume the host application owns the schema, so you get Doctrine mappings rather than migrations. The repository shows no CI signal or install evidence, so any fixture data documenting the intended batch lifecycle is unlikely to be reliable. Write your own factories and feature tests against the vendor-neutral spec you extract.
Weaver
How can I help you explore Laravel packages today?