You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
TextForSpeech v0.18.0
What changed
reshaped the runtime management surface around grouped profiles, style, normalize, and persistence handles instead of exposing whole-profile round-trips as the primary caller workflow
narrowed the profile-management API so callers work with profile summaries, profile details, and targeted replacement mutations rather than feeding full TextForSpeech.Profile values in and out
split the larger runtime source files into role-focused definition and operations files so Profiles, Style, Normalization, and Persistence are easier to navigate and maintain
updated the runtime tests, README, and maintainer guidance to match the streamlined runtime API surface
removed redundant file-header // MARK: comments left behind by the older SwiftFormat configuration while preserving the marks that still separate real internal sections
refreshed the checked-in .swiftformat settings to stop reintroducing those per-type file-header marks
Breaking changes
renamed and reorganized the runtime management API for custom profiles and built-in styles
removed the older runtime.profiles built-in-style accessors and the older whole-profile management methods
Migration notes
callers should use runtime.style.getActive(), runtime.style.list(), and runtime.style.setActive(to:) for built-in style management
callers should use runtime.profiles.getActive(), runtime.profiles.getEffective(), runtime.profiles.get(id:), runtime.profiles.create(name:), runtime.profiles.setActive(id:), and the targeted replacement mutation methods for custom profile management
callers that previously normalized text by pulling profile values out of runtime.profiles should switch to runtime.normalize.text(...) or runtime.normalize.source(...)
maintainers should treat the new runtime file split and the trimmed // MARK: usage as the repository baseline going forward