Swift Formatstyle

by dpearson26998d90fd121a26No license1.1K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 2 months ago

Formats and parses locale-aware numbers, decimals, currencies, percentages, dates, durations, measurements, names, lists, byte counts, and URLs with Foundation FormatStyle and ParseableFormatStyle. Use when replacing legacy Formatter subclasses, designing reusable format APIs, using SwiftUI Text(_:format:), correcting availability, or testing user-facing formatted output across locales.

Instructions onlySoftware Development
AI-generated overview

Guides Swift developers in using Foundation FormatStyle and ParseableFormatStyle for locale-aware display and parsing.

What it does
This skill provides instructions and recipes for formatting and parsing locale-aware values in Swift, including numbers, decimals, currencies, percentages, dates, durations, measurements, names, lists, byte counts, and URLs. It covers selecting built-in styles, availability gating, SwiftUI Text(_:format:) integration, custom FormatStyle creation, common mistakes, and a review checklist. It produces guidance and code patterns rather than executable output.
When to use it
Use it when replacing legacy Formatter subclasses, designing reusable format APIs, integrating formatted values in SwiftUI, correcting availability for iOS 16+ or iOS 18+ APIs, or testing user-facing formatted output across locales.
Requirements
No scripts or runtime dependencies beyond the agent; it references Foundation and SwiftUI APIs and includes a reference document for detailed recipes.

Swift FormatStyle

Use Foundation's type-safe FormatStyle APIs for user-facing display and ParseableFormatStyle when the same convention must accept input. Route String Catalogs, plurals, localized copy, bundles, and RTL layout to ios-localization; formatting still requires locale review even when no text is translated.

Contents

Workflow

  1. Identify the value's semantic type and whether output is display-only or must round-trip through parsing.
  2. Select the narrowest built-in style and keep the user's current locale unless a wire format explicitly requires another locale.
  3. Render the exact UI with representative locales such as en_US, de_DE, ar_SA, and ja_JP.
  4. Check separators, numbering systems, calendars, currency and unit conventions, text direction, and layout.
  5. If output or parsing fails, fix the style or surrounding copy, restore the input fixture, and rerun the same locale matrix.

Load FormatStyle Recipes [blocked] when implementation needs concrete modifiers, date intervals, relative dates, duration patterns, measurements, names, lists, byte counts, or URL component controls.

Quick Reference

ValueDefault styleImportant constraint
Int, Double.numberConfigure precision, rounding, grouping, notation, or sign only as required.
Decimal.number, .percent, .currency(code:)Prefer for exact decimal display and parsing.
Currency.currency(code:)Pass an ISO 4217 code; never hardcode a symbol.
Percent.percentConfirm whether the input is a fraction (0.85) or whole percent (85).
Date.dateTime, .relative, .intervalRelative output should usually stand alone, not be embedded in a sentence.
Duration.time(pattern:), .units(allowed:width:)Requires iOS 16+; choose compact clock output versus labeled units.
Measurement.measurement(width:usage:)usage: controls locale-aware conversion policy.
PersonNameComponents.name(style:)Do not manually concatenate name parts.
Collections.list(type:width:)Let locale rules choose separators and conjunctions.
Byte count.byteCount(style:)Choose file, memory, decimal, or binary semantics deliberately.
URL.urlRequires iOS 16+; query, port, and fragment are opt-in display components.

Selection and Availability

  • Prefer FormatStyle over legacy NumberFormatter, DateFormatter, DateComponentsFormatter, and manual interpolation for new iOS 15+ code.
  • Duration format styles and URL.FormatStyle require iOS 16+.
  • Date.AnchoredRelativeFormatStyle requires iOS 18+ and formats relative to a fixed anchor rather than the current moment.
  • Omit .locale(...) for normal UI so the style inherits the user's locale. Use a fixed locale only for an explicit protocol or test fixture.
  • Treat relative date output as standalone text unless the entire sentence is localized around it.

Docs: FormatStyle

Parsing

Use the matching parseable style when users edit or import formatted values:

swift
let style = Decimal.FormatStyle.Currency(code: "USD")    .locale(Locale(identifier: "en_US"))
let value = try Decimal("$3,500.63", format: style)let display = value.formatted(style)

The fixed locale above is appropriate only because the input contract is explicitly en_US. For normal UI input, use the user's locale and test round trips with representative decimal separators, currency placement, calendars, and numbering systems.

SwiftUI Integration

Prefer Text(_:format:) so SwiftUI owns the formatted value:

swift
Text(price, format: .currency(code: currencyCode))Text(date, format: .dateTime.month().day().year())Text(duration, format: .units(allowed: [.minutes, .seconds]))

For every user-facing formatted Text, preview or test the exact screen across the locale matrix. Use Text(.now, style: .timer), Text(.now, style: .relative), or Text(timerInterval:) for live-updating time displays rather than manually scheduling string refreshes.

Custom FormatStyle

Create a custom style only when built-in composition cannot express the domain convention. FormatStyle refines Codable and Hashable; keep styles as reusable values and add ParseableFormatStyle only when input must round-trip.

swift
struct AbbreviatedCountStyle: FormatStyle {    func format(_ value: Int) -> String {        switch value {        case ..<1_000: "\(value)"        case 1_000..<1_000_000: String(format: "%.1fK", Double(value) / 1_000)        default: String(format: "%.1fM", Double(value) / 1_000_000)        }    }}
extension FormatStyle where Self == AbbreviatedCountStyle {    static var abbreviatedCount: Self { .init() }}

Custom styles still need locale and accessibility review; a compact English suffix may not be suitable for every locale.

Common Mistakes

MistakeFix
Manual formatting or legacy formatter allocation in view codeUse the matching FormatStyle and Text(_:format:).
Hardcoded currency symbol or localePass an ISO currency code and inherit the user locale unless the contract says otherwise.
Binary floating-point for exact decimal inputUse Decimal.FormatStyle and its matching parse strategy.
Assuming URL.formatted() preserves every componentOpt in to .port(.always), .query(.always), or .fragment(.always) only when those components should display.
Relative date output embedded in a larger sentenceKeep it standalone or localize the complete sentence.
Clock-style duration used for proseUse .units(allowed:width:) for labeled output.
Measurement conversion left implicitSelect a usage: appropriate to the UI.
One-locale spot checkRun the same exact-screen fixture across representative locales and fix/rerun failures.

Review Checklist

  • Semantic value type and display-versus-parse requirement identified
  • Built-in FormatStyle used where it can express the convention
  • Availability gated beside iOS 16+ and iOS 18+ APIs
  • Currency uses an ISO 4217 code; exact decimal values use Decimal
  • User locale inherited unless a protocol explicitly fixes it
  • Relative date text stands alone or the full sentence is localized
  • URL components and measurement usage: are deliberate
  • SwiftUI uses Text(_:format:) for formatted values
  • Exact rendered UI and parse round trips pass the representative-locale matrix

References

Source and attribution

Source:dpearson2699/swift-ios-skillsinskills/swift-formatstyleat commit8d90fd1

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from dpearson2699/swift-ios-skills

Widgetkit

dpearson2699

Guides implementing, reviewing, and improving WidgetKit widgets and controls for iOS, iPadOS, watchOS, and CarPlay.

Software Development1.1Kupdated 2 months ago

Weatherkit

dpearson2699

Guides iOS developers in fetching WeatherKit forecasts, alerts, and attribution using WeatherService.

Software Development1.1Kupdated 2 months ago

Vision Framework

dpearson2699

Implement computer vision features including text recognition (OCR), face detection, barcode scanning, image segmentation, object tracking, and document scanning in iOS apps. Covers both the modern Swift-native Vision API (iOS 18+) and legacy VNRequest patterns, VisionKit DataScannerViewController for live camera scanning, and CoreMLRequest/VNCoreMLRequest for custom model inference. Use when adding OCR, barcode scanning, face detection, or custom Core ML model inference with Vision.

Awaiting classification1.1Kupdated 2 months ago

Tipkit

dpearson2699

Implement and review Apple TipKit feature-discovery UI for iOS 17+ apps. Use when adding or auditing in-app tips, contextual help, coach marks, Tip, TipView, popoverTip, rules, events, actions, display frequency, testing overrides, reusable tip identifiers, or iOS 18+ TipGroup and CloudKit tip sync; avoid for generic SwiftUI navigation or layout outside tip presentation.

Awaiting classification1.1Kupdated 2 months ago

Tabletopkit

dpearson2699

Guides building multiplayer spatial board games on visionOS with Apple's TabletopKit and RealityKit.

Software Development1.1Kupdated 2 months ago

Swiftui Webkit

dpearson2699

Guides embedding and controlling web content in SwiftUI apps with WebKit for SwiftUI on iOS 26 and later.

Software Development1.1Kupdated 2 months ago