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.