NSError 域/自定义域 - 约定和最佳实践
NSError 需要一个域，我理解它分段了错误代码的范围。
人们会预料到某个地方存在一个domain.error代码的注册表，但我还没有发现一个。
据说这可以用于查找错误的本地化描述。
有没有人有一套处理错误域和代码的已知最佳实践？权威的参考（主要开发人员或框架制造商）是最佳的，但即使是详细说明良好约定的博客也是有用的。
在您的项目中，您是否维护错误域/代码的注册表，这些注册表映射到本地化描述、恢复、众所周知的用户信息密钥或基于域/代码的错误对象的类似工厂？
或者，您通常只是将一些域和一些代码拼凑在一起，并在定制的 NSError 域中依赖众所周知的用户信息键，例如 NSLocalizedDescriptionKey 等？
NSError requires a domain, which I understand segments the range of error codes.
One would anticipate that there exist somewhere a registry of domain.error code but I've not been able to discover one.
Supposedly this could used for looking up localized descriptions for errors.
Does anyone have any set of known best practices for dealing with error domains and codes? An authoritative reference (major developers or framework makers) is optimal, but even blogs detailing a good convention is useful.
In your projects do you maintain registries of your error domains/codes that map to localized descriptions, recoveries, well known userinfo keys or like factories for your error objects based on domain/code?
Or do you generally just cobble together some domain and some code, and depend on well known userinfo keys such as NSLocalizedDescriptionKey, etc, in your bespoke NSError domains?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
Apple 通常在名为 FrameworkNameErrors.h 的标头中发布其 NS/CFError 代码。例如，Foundation 的错误代码位于 Foundation/FoundationErrors.h 中。此外，他们通常会在框架文档中发布域和代码。
具有自己的错误域和代码的框架的任何独立作者都应该这样做。
Apple generally publishes their NS/CFError codes in a header named FrameworkNameErrors.h. For example, Foundation's error codes are in Foundation/FoundationErrors.h. In addition, they generally publish the domain and codes in their documentation for the framework.
Any independent author of a framework with its own error domain and codes should do the same.