- How do I install inalto/filament-coord-picker in a Laravel app?
- Install it with Composer using composer require inalto/filament-coord-picker. Because it is a Laravel package targeting Filament forms, it almost certainly ships an auto-discovered service provider, so no manual registration should be required. Run vendor:publish afterwards if the package exposes config or migration files. During evaluation, pin the exact version ("inalto/filament-coord-picker": "1.0.12") rather than a floating constraint so automated updates cannot move you across an untested change.
- Does inalto/filament-coord-picker support Laravel 12?
- Version 1.0.12 is the release framed as Laravel 12 compatible, but that claim is an assertion in the release notes rather than evidence from a published CI matrix. Before adopting, diff composer.json between 1.0.11 and 1.0.12 to confirm whether the illuminate/support constraint was widened to include Laravel 12 or narrowed to drop Laravel 10 and 11. Laravel 12 implies PHP 8.2 or newer, so verify your runtime images meet that baseline.
- How do I add a latitude and longitude picker to a Filament resource form?
- The package provides a Filament form field that you add to your resource form schema like any other component, with minimal setup. Users click or drag a marker on an interactive map to set the coordinate pair, and can optionally search an address instead. The README excerpt was not included in the evaluation data, so confirm the exact field class name, namespace, and option methods against the repository before wiring it in.
- Can users search for an address instead of clicking the map?
- Yes, the package overview states that address search is built into the widget alongside click-and-drag marker placement. This is useful when editors know the street address but not the exact coordinates. Address lookup typically relies on an external geocoding service, so verify which provider is used, whether an API key is required, and how failures or rate limits are surfaced to the user.
- How are the picked coordinates saved to my Eloquent model?
- The widget produces a latitude and longitude pair that you map to your model's columns through the form field. Most implementations let you bind two attributes (for example latitude and longitude) or use a single JSON column, so check the field's API for the exact binding behaviour. If your model stores coordinates differently, such as a spatial point type, expect to add a mutator or a custom cast between the field output and your schema.
- What Laravel and PHP versions does this package require?
- The supplied evaluation assumes Laravel 10, 11, or 12 alongside PHP 8.2 or newer, with Laravel 12 as the target for the current release. That assumption is based on the release note wording, not on a dependency manifest, because no composer.json contents were provided in the data. Confirm the illuminate/* and php constraints directly before installing into a pinned legacy application.
- Is inalto/filament-coord-picker production ready?
- It is a 1.0.x package with a double-digit patch count, which suggests active maintenance but a relatively young and still-settling API surface. The evaluation is explicitly provisional: there is no CI or test coverage evidence, no maintainer history, and no download or advisory data in the supplied material. Pin the version, install on a scratch branch, run your existing suite, and review the package's request-lifecycle footprint before treating it as production-safe.
- How do I test a Filament form that uses the coordinate picker?
- Treat it like any other Filament form field test: mount the Livewire component, set the state for the coordinate attributes, and assert the value is saved on submit. Because the widget involves a JavaScript map, browser-level interaction is generally not covered by PHP tests, so focus assertions on the coordinate data contract rather than marker dragging. Note that the package itself publishes no visible test matrix, so you carry the burden of regression coverage for upgrades.
- What is the risk of using a loose ^1.0 constraint with this package?
- Laravel compatibility work landed in a patch release (1.0.12), which is ambiguous: widening constraints to include Laravel 12 is non-breaking, but dropping Laravel 10 or 11 support under a patch number would be a breaking change shipped without a major bump. That is a real hazard if you float on ^1.0 with automated dependency updates enabled. Pin to 1.0.12 or a tight ~1.0.12 during evaluation and diff the composer.json constraint between 1.0.11 and 1.0.12 before loosening it.
- What are the alternatives to this package for map coordinate fields in Filament?
- The common alternatives are other Filament map or coordinate field packages and rolling your own field on top of a mapping library such as Leaflet or Google Maps. Evaluate alternatives on the same criteria used here: a published CI matrix across supported Laravel and PHP versions, clear semantic versioning discipline, more than one active maintainer, and a documented geocoding provider. Since this package has no maintainer or advisory history in the supplied data, compare release cadence and issue responsiveness side by side before committing.