Weave Code
Dao Bundle Laravel Package
setono/dao-bundle
Setono DAO Bundle adds a lightweight data access object layer to Symfony applications, letting you encapsulate database queries in dedicated DAO services for cleaner separation of concerns, easier testing, and reusable persistence logic across your project.
At a glance
Frequently asked questions about Dao Bundle
- Can I use setono/dao-bundle in a Laravel application?
- Not directly. setono/dao-bundle is a Symfony bundle whose value is Symfony DI auto-wiring, and Laravel has no bundle registration or Symfony container compilation. In Laravel you should evaluate the underlying DAO PHP SDK and port the bundle's wiring into a service provider instead of installing the bundle itself.
- Does setono/dao-bundle support Laravel 10 or Laravel 11?
- No Laravel version is supported because the package targets Symfony, not Laravel. It ships a Bundle class, a DependencyInjection extension, and services.yaml, none of which Laravel consumes. Any Laravel 10 or 11 integration would be custom code built on the DAO SDK.
- What does setono/dao-bundle actually do?
- It is a thin Symfony integration layer that registers Setono's DAO PHP SDK clients and configuration in the Symfony service container. The actual data access behaviour lives in the SDK, not the bundle. That distinction matters because the bundle is mostly wiring you would have to recreate in Laravel.
- How do I install setono/dao-bundle with Composer?
- You can run composer require setono/dao-bundle, but in a Laravel project it will add dead code and may pull Symfony packages that conflict with Laravel's own Symfony components. If you only need the DAO functionality, depend on the underlying SDK directly. Treat the bundle as a reference implementation for configuration.
- Why does installing setono/dao-bundle cause Symfony dependency conflicts in Laravel?
- The bundle can require symfony/framework-bundle and other Symfony components, while Laravel already pins its own versions of Symfony contracts and components. Composer may then be unable to resolve a compatible set, or may install versions that break Laravel. Check composer why-not and prefer the SDK to avoid the collision.
- How would I port setono/dao-bundle to Laravel?
- Read the bundle's service definitions and extension class, then recreate the client construction and configuration in a Laravel service provider. Bind DAO interfaces or classes as singletons and publish a config file for credentials and options. This is usually a one-to-three-day job plus tests if the SDK uses plain constructors and PSR-18/PSR-17 HTTP clients.
- Is setono/dao-bundle maintained and safe for production?
- Signals are weak: it has very few GitHub stars, zero dependents, and its last release was October 2023. It appears to be a single-maintainer package with no visible security-response process. If you adopt it, plan to fork it or depend on the SDK, and confirm the SDK's own release cadence and PHP support window.
- What are alternatives to setono/dao-bundle for DAOs in Laravel?
- Laravel's own patterns such as repositories, query objects, action classes, or Eloquent scopes cover most DAO use cases without an extra dependency. If you need the Setono DAO SDK specifically, wrap it in a Laravel service provider and DAO classes. A small sidecar Symfony service is another option if the SDK is tightly coupled to Symfony.
- How do I test DAO services in Laravel if I port setono/dao-bundle?
- Keep the DAO behind an interface and bind a fake or in-memory implementation in your test service provider. Because the bundle only wires services, the testable behaviour is the SDK client calls and your query logic, so assert those with mocked PSR-18 clients or HTTP fakes. Avoid hitting a real database or remote API in unit tests.
- Should I fork setono/dao-bundle to use it with Laravel?
- Forking is reasonable only if you need the bundle's exact wiring and want to maintain it internally, since it is MIT licensed and small. For Laravel, forking the bundle is usually the wrong layer, so fork or depend on the DAO SDK and write a Laravel service provider. Weigh the maintenance cost against simply reimplementing the few service definitions.
Weaver
How can I help you explore Laravel packages today?