- How do I install and configure laravel-dadata in a Laravel app?
- Install it with composer require teleport-kirov/laravel-dadata, publish the package config file, and put your DaData.ru API token in .env. The package registers a service provider and facade alias, so you can resolve the client and call the address, counterparty, or bank methods directly. Setup is quick, and a competent Laravel developer is productive in under a day.
- Which DaData.ru features does this Laravel package support?
- It wraps the DaData.ru HTTP API: address suggestions and normalization, counterparty/EGRUL lookup by INN, bank lookup by BIK, and similar Russian reference-data calls. It is intended for autocomplete and validation in forms, such as checkout, onboarding, and invoicing. Actual endpoint coverage depends on the methods the client exposes, so check the source for what you need.
- Which Laravel and PHP versions does laravel-dadata support?
- The available metadata does not document tested Laravel or PHP versions, and there is no visible CI matrix. Check the illuminate/support constraint in composer.json before assuming support for Laravel 10 or 11. A single tight version pin can block your framework upgrade path and turn the dependency into a fork-maintenance task.
- Is teleport-kirov/laravel-dadata safe to use in production?
- Treat it as unvalidated: it shows zero stars, zero dependents, and no evidence of CI, test coverage, or semver discipline. The repository name references another author's project, which suggests a renamed fork with no community review or exercised bug-finding. If you adopt it, assume you own maintenance, pin the version, and keep it behind your own interface.
- What is the difference between teleport-kirov/laravel-dadata and Pavel-Vinogradov/laravel-dadata-master?
- The package name references Pavel-Vinogradov/laravel-dadata-master, which suggests a renamed fork or vendored copy rather than a tracked upstream fork. There is no stated divergence, changelog, or guarantee that upstream fixes will ever land here. Ask the maintainer directly, or review the diff against upstream before depending on it.
- Does laravel-dadata return typed response objects or raw arrays?
- Thin Laravel wrappers around DaData typically pass decoded response payloads through as raw arrays rather than typed DTOs, though you should verify this in the source. DaData has revised response shapes and added fields over time, so untyped pass-through can surface as undefined index errors in your domain code. Map responses into your own objects at the boundary to contain schema drift.
- How do I test code that calls the laravel-dadata facade?
- The facade is a service-locator-shaped seam, not a domain interface, so tests that hit it directly are brittle. Wrap the client behind your own AddressNormalizer or CounterpartyLookup contract and bind the package implementation in a service provider. In tests, swap in a fake or an HTTP-faked client; there is no evidence the package ships test doubles of its own.
- How should I handle DaData API tokens, retries, and caching with this package?
- Token handling via a published config file plus .env is standard, but confirm the client does not log request URLs containing the token or cache responses with PII to disk. Retry and timeout policy is not documented, so set explicit timeouts in your own wrapper. Cache effectively static reference data such as banks and OKVED yourself to control metered DaData costs, since suggestions fire on keystroke.
- What license applies to laravel-dadata, and can I fork or redistribute it?
- The provided metadata does not state a license, so check the LICENSE file in the repository before redistributing or forking. Because the repo appears to be a fork, also confirm the original project's license terms carry over. Without that clarity, treat the code as something you can use internally but cannot safely republish.
- Are there better alternatives to this package for DaData.ru integration in Laravel?
- Alternatives include calling DaData.ru directly with Laravel's HTTP client and a small in-house client class, or choosing a more established, dependency-reviewed SDK. Given zero dependents and unclear provenance here, a thin in-house client can carry less risk and gives you typed responses and explicit timeout handling. Either way, keep DaData calls behind a contract so you can swap implementations later.