Weave Code
Address Laravel Package
capell-app/address
A Laravel package for managing postal addresses across your Capell applications, with reusable address models, country-aware fields and helpers for storing, formatting and validating addresses consistently.
Reusable, site-scoped countries and structured postal addresses for Capell.
Frequently asked questions about Address
- How do I install capell-app/address in a Laravel application?
- Install it with Composer using composer require capell-app/address, then publish the package configuration and migrations. Run the migrations and any provided seeders so the country and subdivision reference data is available. Because the current line is beta, pin an exact tag such as v1.1.0-beta.47 in composer.json rather than allowing automatic beta updates.
- Does capell-app/address support polymorphic address relations?
- Yes. The package provides an Eloquent address model with polymorphic relations so addresses can be attached to users, orders, or any other model. A practical approach is to keep package models beneath your domain layer and expose a thin local wrapper or DTO rather than letting the package model become your public domain model. That reduces the blast radius if the beta API changes.
- Which Laravel and PHP versions does capell-app/address support?
- The provided package overview and release information do not declare a supported Laravel and PHP version matrix. Check the package composer.json constraints and any CI configuration before adoption, and test against the exact Laravel and PHP versions your application runs. Treat each beta release as unverified until you have confirmed compatibility yourself.
- Is capell-app/address safe to use in production?
- It should not be treated as production-safe without safeguards. The current release is v1.1.0-beta.47, deep inside a beta line with high API instability, and the release note is only a changelog compare link with no summarized changes or breaking-change callouts. For production, pin an exact tag, read the diff yourself, and specifically review schema, seed-data, and public API changes before deploying.
- Where does the country and subdivision data in capell-app/address come from?
- The package provides country and administrative subdivision data, but the overview does not document an upstream source such as ISO 3166 or CLDR or a refresh process. Address reference data changes over time through country renames, subdivision splits, and other real-world updates, so ask the maintainers how the dataset is maintained. Treat data freshness as a medium risk until a documented update cadence exists.
- How do I format and validate addresses with capell-app/address?
- The package includes address formatting and validation helpers intended to keep storage, formatting, and validation consistent across your application. Use those helpers for shared address rules, but keep application-specific requirements such as delivery constraints or regional quirks in your own wrapper layer. Validate country and subdivision values against the package reference data rather than hard-coding lists in your app.
- Can I use capell-app/address outside a Capell application?
- It is a Laravel package from the Capell ecosystem, so the main question is coupling rather than framework compatibility. If it is genuinely standalone, it can save you from hand-rolling country, subdivision, and address tables in any Laravel app. If it pulls in Capell support packages or assumes Capell conventions, you may be adopting a fragment of a CMS you do not otherwise run, so inspect the transitive dependency footprint first.
- What changed between capell-app/address beta.43 and beta.47?
- The published release note for v1.1.0-beta.47 is a bare changelog compare link from beta.43 to beta.47, with no summarized feature list, breaking-change callout, or migration guidance. That means you need to read the diff yourself and identify which changes touch the schema, seed data, or public API. This is a release-hygiene concern to raise with the maintainers before adoption, not after.
- How should I handle migrations and existing address data with capell-app/address?
- Publish the package migrations and review them before running them against any database that already contains address records. Confirm whether migrations are additive-only or alter existing tables in place, because schema and seed-data changes are the dangerous class in an address package and can corrupt records without throwing an exception. Back up existing data, test seed updates in staging, and pin the exact beta tag you validated.
- What are the alternatives to capell-app/address for Laravel postal addresses?
- Alternatives include a thin in-house Laravel address model backed by ISO 3166 or CLDR reference data, or another maintained Laravel address package with a documented Laravel and PHP support matrix. Compare them on data refresh process, migration safety, polymorphism support, and how actively release notes are maintained. If you only need simple address storage, a small local model plus a maintained country dataset may carry less beta risk than adopting a deeply beta package.
Weaver
How can I help you explore Laravel packages today?