- What is heloufir/filament-leaflet-geosearch used for?
- It is a Filament form field that wraps Leaflet.js and the Leaflet GeoSearch plugin. It lets users search for addresses and select latitude and longitude coordinates visually on a map. You add it to a Filament admin form when you need a location picker that persists a lat/lng pair.
- Does heloufir/filament-leaflet-geosearch support Filament v3 or v4?
- The package is strongest for Filament v2-era applications, based on its release cadence and last release date of 2022-09-22. There is no evidence in the provided evaluation that it supports Filament v3 or v4, and it likely declares a filament/filament ^2.x constraint. Verify composer.json in a spike, because v3/v4 use will probably require a fork.
- How do I install heloufir/filament-leaflet-geosearch in Laravel?
- Installation is mechanically simple: Composer require the package, publish its assets, register the field in a Filament form schema, and configure the geocoding provider options. The evaluation notes no queue workers, migrations, or service providers beyond Filament auto-discovery. Check the README for the exact asset publish command and field namespace.
- Which geocoding provider does Leaflet GeoSearch use by default?
- Leaflet GeoSearch itself is provider-agnostic and can work with Nominatim, Bing, Google, LocationIQ, and similar services. The provided evaluation does not confirm whether this package exposes clean provider configuration or hard-codes a default. Verify the default provider and swapability before relying on it, especially for commercial or high-volume use.
- Can I self-host the geocoder with this Filament Leaflet field?
- The evaluation flags self-hosting as an open question: the package may or may not expose provider configuration cleanly. Because Leaflet GeoSearch is provider-agnostic, self-hosting is feasible if the field lets you point at your own Nominatim instance. If the provider is hard-coded, plan to fork the field.
- How does the field store latitude and longitude in the database?
- The field yields a latitude/longitude pair and possibly a display label, but the provided evaluation says it is unclear whether it persists a structured object, JSON, or two separate columns. Test round-tripping on both create and edit forms. Regardless of storage shape, re-validate coordinates and bounds server-side because client-side geocoding cannot be trusted for validation.
- Does heloufir/filament-leaflet-geosearch support reverse geocoding?
- Reverse geocoding is not confirmed in the provided evaluation. Leaflet GeoSearch is primarily known for forward address search, so map click to address behavior should be tested explicitly. If you need reverse geocoding and the field lacks it, you will need custom work or a fork.
- Is heloufir/filament-leaflet-geosearch maintained and safe for production?
- Treat it as high-risk for production: the last release was roughly three years ago and the project has about 22 stars, so there is effectively no upstream maintenance or security patching. The evaluation recommends adopting only as a convenience input and planning a fork-and-own path. Keep server-side validation and consider a maintained alternative if the location picker is business-critical.
- How are assets registered in heloufir/filament-leaflet-geosearch?
- The evaluation suggests the field likely ships pre-built JavaScript and CSS through an older Filament asset registration API rather than a Vite pipeline. Modern Filament versions expect Vite-built assets, so the field may break silently when the host app upgrades Filament. Confirm how assets are registered and whether they survive your build pipeline.
- What are alternatives to heloufir/filament-leaflet-geosearch?
- The provided evaluation does not name a specific maintained alternative. It advises checking for a maintained fork or credible alternative before adopting this package as fork-and-own. Evaluate current Filament map or location picker fields that support your Filament major version and asset pipeline.