- Is baks-dev/avito-orders compatible with Laravel 11 or 12, and what PHP version is required?
- The package requires PHP 8.4+, which aligns with Laravel 12.x. For Laravel 11.x, you’ll need PHP 8.3+, but the package explicitly targets PHP 8.4+, so test thoroughly for compatibility. Check the [README](https://github.com/baks-dev/avito-orders) for updates, as Laravel 11’s Facade changes may cause integration issues.
- How do I set up Avito FBS/DBS profiles, payments, and delivery in Laravel?
- Run the provided Artisan-like commands via Symfony’s `bin/console` (not Laravel’s `artisan`). For FBS, execute `php bin/console baks:users-profile-type:avito-fbs`, `baks:payment:avito-fbs`, and `baks:delivery:avito-fbs`. For DBS, replace `fbs` with `dbs`. These commands configure Avito-specific profiles, payment methods, and delivery options in your database.
- Does this package work with Laravel’s Eloquent ORM, or will it conflict with existing database schemas?
- The package introduces Avito-specific tables (e.g., `avito_orders`, `delivery_methods`) and relies on Symfony’s Doctrine ORM by default. To avoid conflicts, either use a separate database schema for Avito data or create custom Eloquent models that map to the same tables. Test migrations carefully to prevent schema collisions.
- Can I use baks-dev/avito-orders without adopting the entire baks-dev/core Symfony bundle?
- No, the package has a hard dependency on `baks-dev/core:^7.4`, which is Symfony-centric. If you reject Symfony’s architecture (e.g., HttpKernel, EventDispatcher), you’ll need to refactor the core logic into Laravel services or use a microservice approach. This may require significant customization to replace Symfony-specific features like CLI commands or event listeners.
- Are there Laravel-native alternatives to baks-dev/avito-orders for Avito marketplace integrations?
- For lightweight Avito API interactions, consider `avito/marketplace-api` (official SDK) or generic Laravel packages like `webkul/laravel-marketplace`. These avoid Symfony dependencies but lack Avito-specific features like FBS/DBS profile types or CLI-driven setup. Evaluate whether you need the bundle’s full workflow or if a custom wrapper (e.g., Guzzle + Eloquent) suffices.
- How do I handle Avito payment webhooks or order lifecycle events in Laravel?
- The package likely uses Symfony’s EventDispatcher for webhooks. To integrate with Laravel, wrap Symfony events in Laravel’s `Event` facade or use a message broker (e.g., Laravel Queues with RabbitMQ). For example, listen for `avito.order.created` events in Symfony and dispatch Laravel events like `OrderCreated` to trigger jobs or notifications.
- What’s the best way to test baks-dev/avito-orders in a Laravel project?
- Run the provided PHPUnit tests with `php bin/phpunit --group=avito-orders`, but note these may rely on Symfony’s testing tools. For Laravel-specific tests, mock Symfony dependencies (e.g., `HttpKernel`, `EventDispatcher`) using Laravel’s `Mockery` or `Pest`. Test CLI commands by calling `bin/console` directly in your test environment.
- Will this package work in production, or do I need to modify Symfony’s HttpKernel for Laravel?
- The package is designed for production but requires Symfony’s HttpKernel, which may introduce overhead. For a cleaner Laravel integration, consider Option 2 (custom wrapper) or Option 3 (microservice) from the TPM assessment. Benchmark request latency with Blackfire.io if using the Symfony bridge, as HttpKernel can slow down Laravel’s request lifecycle.
- How do I configure the package to avoid conflicts with Laravel’s service container or Facades?
- The package uses Symfony’s service container, so bind its services manually in Laravel’s `config/app.php` or use a package like `spatie/laravel-symfony` to bridge containers. Replace Symfony Facades (e.g., `EventDispatcher`) with Laravel equivalents (e.g., `event()` helper) in your custom wrappers. Test Facade deprecations in Laravel 11/12, as they may break Symfony’s assumptions.
- Is there English documentation or support for Laravel-specific issues with this package?
- The primary documentation is in Russian, but the README includes basic setup steps. For Laravel-specific issues, check the GitHub issues tab or contact the maintainers directly. The package’s last release is marked for 2026, so validate the roadmap for ongoing Laravel compatibility. Consider contributing translations or Laravel-specific guides to the project.