- What is 3neti/report-registry used for in Laravel?
- It is a Laravel package for building a central registry of reports. You define and register report classes once, then discover and manage them consistently across your application. This helps with listing reports and integrating them into dashboards, APIs, or scheduled jobs.
- How do I install 3neti/report-registry with Composer?
- Install it as a Composer dependency in your Laravel project, normally with composer require 3neti/report-registry. After that, follow the package README for any service provider, configuration, or publishing steps. The provided overview does not list exact installation details, so the README should be your source of truth.
- How do I register a report class with the registry?
- Define your report class and register it once with the package registry. The registry then provides a consistent way to discover and manage that report throughout your app. Check the README for the exact registration API and expected class structure.
- Does 3neti/report-registry support Laravel 10 and Laravel 11?
- The provided context does not specify supported Laravel versions. Check the package composer.json and README for version constraints before installing or upgrading. Do not assume compatibility with a specific Laravel release until it is confirmed there.
- Can I list all registered reports for a dashboard or API?
- Yes, the package is intended to make reports easier to list and integrate with dashboards and APIs. Once report classes are registered centrally, you can retrieve them consistently instead of maintaining scattered references. The exact listing API depends on the package documentation.
- Can report registry reports be used in scheduled jobs?
- The package blurb specifically mentions integration with scheduled jobs. After registering reports once, scheduled jobs can reference them consistently through the registry. Review the README for the recommended way to execute or generate a registered report.
- Do I need to publish configuration files for report-registry?
- The provided overview does not include configuration or publishing details. Many Laravel packages work with sensible defaults and only require publishing when you need to override settings. Check the README for whether configuration publishing is required for 3neti/report-registry.
- How should I test a Laravel app that uses report-registry?
- Use your normal Laravel testing setup and register test report classes in the registry as part of each test. Then assert that discovery, listing, and any report generation integration behave as expected. Check the package documentation for test helpers or recommended isolation patterns.
- Is 3neti/report-registry suitable for production use?
- It can be a reasonable production choice for central report management in Laravel, but confirm maintenance status, Laravel version compatibility, and test coverage first. The provided context does not include release history or maintenance details. Review the repository and composer.json before adopting it in a production application.
- What are alternatives to using a report registry package?
- Alternatives include manually registering reports in a service provider, using Laravel container tagging, or building a custom report manager. A dedicated registry package can reduce duplication and make report discovery more consistent. Choose based on how many reports you manage and how much integration you need across dashboards, APIs, and jobs.