sealed_countries 是一个 Flutter/Dart 包,使用密封类提供全面的国家数据,确保类型安全和不可变性。它包含国家名称、代码和区域等信息,非常适合需要可靠国家选择或代码查找的应用程序。该包设计了清晰、结构化的数据模型,并支持 Android、iOS、Web、macOS、Windows 和 Linux 多个平台。其密封类方法可防止意外扩展,提升代码可维护性。
适合场景
国家选择器 UI 组件
国际化 (i18n) 设置
电话号码或地址表单验证
货币和语言区域映射
与国家数据的API集成
主要特点
基于密封类的国家数据模型
类型安全的国家枚举
支持所有主要平台
不可变且可预测的数据结构
全面的国家元数据
适合对象
开发多语言应用程序的开发者
表单验证需要国家代码
需要国家选择界面的应用程序
注重数据建模类型安全的团队
面向跨平台部署的项目
使用建议
需要理解 Dart 中的密封类
仅限静态国家数据(无实时更新)
由于生成的代码,构建大小可能会略有增加
原始 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.