국가 정보를 밀봉하고 불변으로 제공하는 플러터 패키지로, 국가 선택기, 전화 코드 선택기, 통화 선택기를 포함합니다. 성능과 타입 안정성을 고려하여 제작되었으며, 국제화 및 현지화 작업을 위한 깔끔하고 사용하기 쉬운 API를 제공합니다. 이름, 코드, 전화 접두사, 통화 등 사전에 정의된 최신 국가 정보가 모두 플러터 위젯 형태로 구조화되어 있습니다. 국가 선택 또는 지역 설정이 필요한 앱에 적합합니다.
사용 사례
국제 앱 로컬라이제이션
국가 코드를 포함한 전화번호 입력
금융 앱에서 통화 선택
사용자 프로필 국가 선택
다중 지역 전자상거래 플랫폼
주요 기능
타입 안전성을 위한 시ール드 클래스 설계
국가 선택기용 사전 구축된 Flutter 위젯
포괄적인 국가, 전화 및 통화 데이터
다중 플랫폼 지원
pub add를 통한 간편한 통합
불변 데이터 구조
적합한 대상
글로벌 앱을 개발하는 개발자
국가/지역 선택이 필요한 앱
현지화 및 i18n 프로젝트
국가 코드가 있는 폼 입력
크로스 플랫폼 모바일 및 웹 애플리케이션
고려 사항
피커 UI의 사용자 정의 제한
데이터는 정적이며 패키지 버전을 통해 업데이트해야 합니다
실시간 국가 데이터 동기화 없음
동적 국가 목록에는 적합하지 않습니다
픽커에서 상태를 수동으로 처리해야 합니다
원본 README
연결된 소스 저장소의 README 원문 스냅샷입니다. 최신 내용은 저장소에서 확인하세요.
Sealed World
A pure Dart, fully tested and ISO-driven ecosystem for the world's data in the form of compile-time, tree-shakable constant classes with a sealed origin.
[!TIP]
Flutter packages use world prefix, Dart packages use sealed prefix for core functionality and l10n prefix for localization maps.
This ecosystem follows a hierarchical structure with optional localization support. At the foundation are languages and scripts, providing core functionality across all packages. Building upon this, currencies extend the system, followed by countries. Each core package has an optional l10n companion that provides localization maps. The countries package serves as a bridge to Flutter, enabling the rendering of country flags, which the world_countries package uses to create UI components like country pickers with localized names and visual elements.
This section explains how the ecosystem handles SDK pinning, semantic versioning, and release cadence, and why this approach benefits users and contributors.
SDK Compatibility and Pinning
Pinning to the Dart version bundled with Flutter stable ensures local developer environments match CI, minimizing SDK mismatches and hard-to-reproduce issues. The Flutter SDK archive lists each Flutter stable release together with its bundled Dart version Flutter SDK archive.
Production packages target Dart stable rather than beta/dev, in line with Dart's guidance to use stable for building and deploying apps Get the Dart SDK.
Formatter and workspace changes introduced around Dart 3.7/3.8 can create large diffs when mixing pre/post language versions. Dart 3.8 includes a rewritten/updated formatter behavior; formatting changes apply when the package opts into the newer language version Announcing Dart 3.8, Breaking changes (formatter behavior >=3.8).
Semantic Versioning
Semantic Versioning is followed: MAJOR for breaking changes, MINOR for new features, PATCH for bug fixes Semantic Versioning.
Dart's pub ecosystem applies SemVer for resolution and documents conventions including pre-1.0 handling and "next breaking" logic Package versioning.
Release Cadence
Major releases: approximately once per year, potentially including breaking changes; aligned after Flutter/Dart stable cycles to reduce churn Semantic Versioning.
Minor releases: about once per month for feature additions (especially for Flutter-facing packages), without breaking changes Package versioning.
Patch releases: as needed for fixes and docs, with no API changes Package versioning.
Deprecated APIs are removed only after reaching end of life in a subsequent stable release cycle, consistent with Flutter's deprecation policy and examples across releases (e.g., removals after 3.7, 3.13, 3.19).
Migration guidance is linked in release notes for major removals, reducing friction and helping teams adopt changes in predictable windows Flutter breaking changes and migration guides.
Rationale
Aligning with Flutter stable's Dart ensures consistent environments across CI and contributors, reducing surprise failures and easing support Flutter SDK archive.
Benchmark & regression verification system
This package includes an automated benchmark system that runs on every release to detect performance regressions. Each version produces immutable JSON artifacts containing build metadata (APK size, toolchain versions, Android configuration) and runtime metrics (startup time, frame performance, memory and CPU usage, etc.).
[!TIP]
These artifacts are attached to GitHub Releases and committed to the repository, enabling historical comparison and transparent performance tracking across versions. The benchmark flow uses low-end physical ARM64 Android devices with Flashlight + Maestro for reproducible, device-driven testing.
To run benchmarks locally or learn more about the system, see the benchmarks documentation. Execute the shared CLI via dart run tools/bin/benchmarks.dart $package_name (or cd tools && dart run :benchmarks $package_name). Current targets include all Flutter packages. All benchmark data is immutable and versioned, ensuring full auditability and regression traceability.
[^1]: While sealed_languages technically depends on l10n_languages for localization, this is not part of its core functionality. The package primarily serves as the backbone for all sealed_* and world_* packages by providing typed locale classes and extensions that power localization maps across the entire ecosystem.