- How do I install shude/laximo-bundle in a Laravel application?
- Install it with Composer using composer require shude/laximo-bundle. The package provides Laravel service-container bindings and a facade, so it should register through normal package discovery or its service provider. After installation, publish the configuration and add your Laximo credentials before making catalog queries.
- How do I configure Laximo API credentials and endpoints in Laravel?
- The package is config-driven, so credentials, API endpoints, and locale settings belong in the package configuration file rather than in application code. Publish the config into your Laravel config directory and set values through environment variables where appropriate. Because values are loaded through Laravel config, clear or rebuild cached configuration after changing them.
- Which Laravel and PHP versions are supported by shude/laximo-bundle?
- The supplied package information does not publish a supported PHP or Laravel version matrix. Check the package composer.json for its php and illuminate or laravel constraints before adopting it, especially if your application is pinned to an older framework minor. Then run a composer why-not check against your lock file to confirm the package resolves cleanly.
- How do I query vehicle makes, models, modifications, and OEM part numbers with this package?
- The bundle exposes Laximo catalog operations through its configured services and facade, covering vehicle catalogs, units, and OEM cross-references. Use those bindings instead of writing your own HTTP client calls, and consult the README for the exact method names available in your version. Responses map to Laximo catalog concepts such as makes, models, modifications, and parts data.
- Does shude/laximo-bundle provide a facade and service container bindings?
- Yes. The package advertises service-container bindings and a facade for quick access to Laximo services inside Laravel. That means you can dependency-inject the underlying service or resolve it through the facade in controllers and application services. Prefer constructor injection where you need testability and explicit dependencies.
- How do I publish the Laximo configuration file in Laravel?
- Use Laravel's vendor publish command to copy the package configuration into your application config directory, for example php artisan vendor:publish with the package's provider or tag. The package lists publishable configuration as a feature, which supports per-environment setups. Confirm the exact publish tag in the README or service provider if the default command lists multiple packages.
- How does shude/laximo-bundle handle Laximo API errors?
- The package uses Laravel-native exceptions, so failures from the Laximo integration are intended to be caught and handled like other Laravel exceptions. Wrap catalog calls in try and catch blocks where a failed lookup should fall back to cached data or a user-facing message. Check the README for the specific exception classes shipped by your installed version.
- Is shude/laximo-bundle production ready, and what should I check before adopting 1.0.0?
- Treat 1.0.0 as a fresh baseline because no release notes or changelog were supplied, and verify the package's constraints and global registrations before using it in shared code. Confirm it does not register global middleware, model scopes, or observers that change application-wide behaviour, and make sure any boot-time environment reads work with config:cache. Install it into a single non-critical service first and test dependency resolution against your host composer.lock.
- How can I test Laximo integration in Laravel without calling the live API?
- The supplied information does not document dedicated testing helpers or fake clients. In a Laravel application, bind a test double or mock for the Laximo service in the container so your code resolves the fake during tests. Keep live API calls out of the default test suite and assert against recorded or stubbed catalog responses instead.
- What are the alternatives to shude/laximo-bundle for Laximo integration?
- The main alternative is calling the Laximo API directly with Laravel's HTTP client or an existing Laximo SDK and wrapping it in your own service class. This bundle's value is its config-driven setup, service bindings, and facade, so compare that convenience against maintaining your own thin client. Check whether a better-maintained first-party or vendor-supported Laximo library exists before committing to the package.