- Is florianajir/datanova-bundle a Laravel package?
- No. It is a Symfony bundle that registers through Symfony's dependency-injection extension and configuration tree, consumed by Symfony's kernel rather than Laravel's service provider and facade model. There is no package discovery, no Laravel service provider, and no facade. Using it in Laravel means hand-registering Symfony container semantics or running it as a sidecar.
- Can I install datanova-bundle in a Laravel 10 or 11 app?
- Almost certainly not without pain. Release 0.4.1 targets roughly PHP ^7.x with symfony/* ^5.0, while Laravel 10 and 11 ship Symfony 6.4 and 7 components. Composer will either fail outright or force a global downgrade of your framework dependencies. Read the package composer.json before attempting anything.
- How do I install and configure datanova-bundle?
- Install it with Composer, register the bundle in your Symfony kernel, then describe your grid in bundle configuration and render it in a Twig template. Per-dataset options and columns are set through the configuration tree. All of this assumes a Symfony 5-era runtime, not a Laravel application skeleton.
- Does datanova-bundle support filtering, sorting and pagination?
- The package advertises built-in filtering, sorting and pagination for large result sets, plus Twig helpers for rendering tables without boilerplate. The underlying intent is that controllers and templates stay thin. In a Laravel rewrite you would implement these with the query builder and Eloquent pagination instead.
- Is datanova-bundle still maintained?
- No. The last release, 0.4.1, is dated 2020-04-19, with 15 stars and zero dependents. A single pull request performing a controller refactor is a version-compatibility errand, not a maintenance cadence. There is no triage commitment, no security process and no roadmap.
- What Symfony and PHP versions does datanova-bundle 0.4.1 support?
- Version 0.4.1 exists specifically to move its controllers onto Symfony 5, so the supported envelope is roughly PHP ^7.x with symfony/* ^5.0. That is the framework generation before the Symfony 6.4 and 7 components that Laravel 10 and 11 depend on. Treat composer.json as the gating read before any evaluation.
- How do I test a DataNova integration in Laravel?
- Use the Laravel Http facade with Http::fake() to stub the DataNova endpoints, and bind a fake DataNovaClient implementation in the container for unit tests. That keeps tests fast and free of network calls. Relying on the bundle's Symfony service definitions inside a Laravel test suite is impractical.
- What is the best Laravel alternative to datanova-bundle?
- Rewrite rather than adopt. Build a DataNovaClient interface with an HttpDataNovaClient implementation using Laravel's Http facade, a config/datanova.php for base URI, key and timeout, typed DTOs for responses, and a fake for tests. That is roughly 200 to 300 lines, fully owned, with no version conflicts. The bundle is best harvested for ideas, not code.
- Can I run datanova-bundle as a sidecar service instead of installing it in Laravel?
- Yes, and 0.4.1 makes this marginally more concrete because its refactored Symfony 5 controllers can be mounted in a minimal Symfony app exposing an internal REST endpoint. It quarantines the aged dependency away from your Laravel codebase. The trade-off is an extra deployable plus a pinned Symfony 5 runtime you must patch yourself.
- Is the DataNOVA API still available, and what are its licensing and rate limits?
- Unverified. Release 0.4.1 was framework plumbing, not endpoint or payload remediation, so the client still encodes 2020-era DataNOVA endpoint and response assumptions. API key provisioning, quota terms, SLAs and whether the Open Data endpoints still exist unauthenticated all need checking independently of this package. Also confirm whether DataNOVA is the right source for your actual need, or whether a maintained SDK or domestic alternative exists.