将错误映射为界面消息
将失败转换为本地化且易于用户理解的文本
将错误映射为界面消息 是 CoddyKit 上的免费 Kotlin Multiplatform Academy 课时。 这是第 3 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Kotlin Multiplatform Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Kotlin Multiplatform Academy 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Raw Errors Are Cryptic
A user should never see SerializationException on screen. Your job is to translate technical failures into calm, human sentences.
Define Friendly Categories
Group failures into a few error kinds like network, server and unknown. Each kind maps to one clear message the apps can show.
enum class ErrorKind { NETWORK, SERVER, UNKNOWN }Carry the Kind in Failure
Extend your Failure to hold an ErrorKind, not just a raw string. The UI then decides wording instead of trusting backend text.
data class Failure(val kind: ErrorKind) : Result<Nothing>()Map at the Boundary
Convert exceptions to an ErrorKind right where you catch them. After this point your code speaks only in friendly, stable categories.
catch (e: IOException) {
Failure(ErrorKind.NETWORK)
}A Message Lookup
Write one function that turns an ErrorKind into display text. Keep it in shared code so both apps phrase errors identically.
fun message(k: ErrorKind): StringLocalize the Text
Real apps translate messages. Let each platform localize the kind, so the shared layer passes the category and the UI picks the language.
Keep Strings Out of Logic
Your rules return an ErrorKind, never a hardcoded sentence. Wording can change anytime without touching business logic.
Different Kinds, Different UI
A network error might show a retry button while a server error shows a support link. The kind drives both the words and the action.
Fallback for the Unknown
Always include an UNKNOWN kind. Unexpected failures still get a polite, generic message instead of a blank or scary screen.
Test the Mapping
Because the mapper is pure, you can test it in commonTest: feed an exception, assert the kind, with no UI or device involved.
One Source of Truth
Now errors travel as typed kinds from catch to screen, giving Android and iOS one consistent, friendly story for every failure.
Quick Check
Consider what the shared layer should expose to the UI.
Recap
You categorized failures into ErrorKinds, mapped exceptions at the boundary, and let each UI localize and act on the kind for a friendly experience. 💬
常见问题解答
「将错误映射为界面消息」课时是免费的吗？
是的 — 「将错误映射为界面消息」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Kotlin Multiplatform Academy 课程的其余内容，请升级到 CoddyKit PRO。 Kotlin Multiplatform Academy 课程共包含 4 节课。
「将错误映射为界面消息」这节课中我会学到什么？
将失败转换为本地化且易于用户理解的文本 你通过在浏览器中直接运行的动手代码来练习 Kotlin Multiplatform Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Kotlin Multiplatform Academy 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Kotlin Multiplatform Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 3 节课，共 4 节。
「将错误映射为界面消息」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Kotlin Multiplatform Academy 课中编写并运行代码吗？
能。每节 Kotlin Multiplatform Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。