- Is this package compatible with Laravel 8/9/10 or only Symfony 3.x?
- This package is hardcoded for Symfony 3.1.x and won’t work natively in Laravel. You’d need to abstract it via a wrapper or fork it for Laravel compatibility, which isn’t officially supported. Laravel’s ecosystem relies on modern PHP (8.x+) and Symfony 5/6/7, so this package introduces significant versioning risks.
- Can I use this for anything other than city autocomplete?
- No, this package only handles Google Maps Places API for city autocomplete. For directions, geocoding, or static maps, you’d need to integrate the official Google Maps JavaScript API directly or use a separate library. The package’s limited scope may force you to mix solutions, increasing complexity.
- How do I install this in Laravel if it’s a Symfony bundle?
- You can’t install it directly in Laravel due to Symfony dependencies. You’d need to manually extract the relevant logic (e.g., Guzzle HTTP calls for Places API) and adapt it to Laravel’s service container and routing. This requires rewriting the bundle’s monolithic design, which isn’t trivial.
- Does this package support modern PHP (8.x) or only PHP 5.5+?
- The package requires PHP ≥5.5.9 but lacks type hints, PSR-12 compliance, or modern dependency injection practices. Upgrading it to PHP 8.x would require significant refactoring, including adding return types, strict typing, and fixing deprecated functions. The last release was in 2016, so no official support exists.
- Will this work with React/Vue or other SPAs without jQuery?
- No, this package mandates jQuery and jQuery UI, which may conflict with modern SPAs. If your app already uses these libraries, integration is straightforward, but for React/Vue or vanilla JS projects, you’d need to rewrite the frontend logic or use the Google Maps JavaScript API directly for better compatibility.
- How do I securely manage my Google Maps API key with this package?
- The package hardcodes API keys in templates (e.g., `renderCitySuggest`), which is a security risk. To mitigate this, manually inject the key via Laravel’s `.env` file or the `config/services.php` file and pass it dynamically to the bundle’s controller. Avoid hardcoding in templates to prevent exposure.
- Are there alternatives to this package for Laravel?
- Yes, consider using the official [Google Maps JavaScript API](https://developers.google.com/maps/documentation/javascript/overview) for client-side autocomplete or server-side solutions like [Laravel Google Maps](https://github.com/stevebauman/location) for geocoding. These are actively maintained and support modern Laravel versions without legacy dependencies.
- Does this package handle API rate limits or errors gracefully?
- No, the package lacks built-in rate limiting, retry logic, or adaptive error handling for Google Maps API failures. If the API returns errors (e.g., quota exceeded, service outage), the bundle will throw exceptions without fallback mechanisms. You’d need to implement custom error handling or use a wrapper with resilience features.
- Can I use this in a microservice architecture or headless Laravel app?
- No, the package is tightly coupled to Symfony’s `AppKernel.php` and `routing.yml`, making it unsuitable for microservices or headless setups. To adapt it, you’d need to decouple the logic from Symfony’s monolithic structure and refactor it into a standalone service or API, which isn’t officially supported.
- Is this package actively maintained? What’s the risk of using it?
- The package is abandoned, with no updates since 2016 and a single maintainer. Risks include breaking changes from Google’s API updates, unpatched security vulnerabilities in Symfony 3.x/PHP 5.5, and Guzzle v6.2 deprecation. For production use, evaluate the cost of maintaining a legacy dependency versus switching to a modern alternative.