- What Laravel versions does baks-dev/products-stocks support?
- The package targets Laravel 10+ (or 9.x) based on Doctrine migrations and Artisan command usage. Test thoroughly with your specific version, as no explicit Laravel version is declared. PHP 8.4+ is a strict requirement, so older Laravel stacks may need upgrades.
- How do I install and configure this module in a Laravel project?
- Run `composer require baks-dev/products-stocks`, then execute `php artisan baks:assets:install` to set up configuration and assets. Use `php artisan doctrine:migrations:diff` and `php artisan doctrine:migrations:migrate` to apply database schema changes. Override defaults via config files if needed.
- Does this package support multi-warehouse inventory management?
- Yes, the module includes warehouse logic for distributed inventory. However, scalability for global operations depends on custom extensions or additional configuration. Review the migration schema for warehouse-related tables (e.g., `warehouses`, `stock_movements`) to confirm feature coverage.
- Can I integrate this with existing Eloquent models instead of Doctrine?
- The package assumes a Doctrine ORM setup, but you can adapt it for Eloquent by implementing repository patterns or custom query builders. Check the migration files for table structures and replicate them in Eloquent models. Some service contracts may need adjustments for Eloquent compatibility.
- Are there event listeners for stock updates (e.g., low-stock alerts)?
- The package does not explicitly document event listeners, but it likely supports stock-related events (e.g., `StockUpdated`). Review the source code for event dispatching in stock services or repositories. Custom listeners can be added via Laravel’s event system if needed.
- How do I test this module in my Laravel application?
- Run `php artisan test --group=products-stocks` to execute module-specific tests. For integration testing, mock dependencies like product models or warehouse services. Use PHPUnit’s `--filter` flag to isolate stock-related test cases. Document edge cases (e.g., concurrent stock updates) in your test suite.
- What databases does this package support?
- The module uses Doctrine migrations, so it supports MySQL, PostgreSQL, and SQLite out of the box. SQL Server is not explicitly mentioned, so test thoroughly if using it. Ensure your database collation and encoding (e.g., UTF-8) match the module’s requirements.
- How do I handle failed migrations or data corruption?
- Doctrine migrations include rollback support, so failed migrations can be reverted with `php artisan doctrine:migrations:migrate --down`. For data corruption, implement transactional logic in stock services and use database backups. The package lacks explicit rollback documentation, so review migration scripts for custom logic.
- Are there alternatives to this package for Laravel stock management?
- Alternatives include `spatie/laravel-inventory`, `torchlight/laravel-stock`, or custom solutions using Eloquent. Compare features like multi-warehouse support, reporting, and API integrations. This package stands out for its Doctrine ORM integration and modular design, but evaluate whether its PHP 8.4+ requirement aligns with your stack.
- How do I extend or customize stock movement logic?
- Extend the module by creating custom services or repositories that override default behavior. Hook into stock events (if supported) or modify migration files for schema changes. Document customizations in your project’s architecture guide to ensure maintainability. Test extensions in isolation before merging with production.