{"id":35992,"date":"2022-05-25T14:15:54","date_gmt":"2022-05-25T18:15:54","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=35992"},"modified":"2022-05-25T20:26:04","modified_gmt":"2022-05-26T00:26:04","slug":"attributedstring-attribute-scopes","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/05\/25\/attributedstring-attribute-scopes\/","title":{"rendered":"AttributedString Attribute Scopes"},"content":{"rendered":"

Natalia Panferova<\/a>:<\/p>\n

UIKit and AppKit attribute scopes have many attributes with matching names but different value types. Attributes with types defined in UIKit such as UIColor<\/code>, UIFont<\/code> etc. are available on platforms that can import UIKit and attributes with types defined in AppKit such as NSColor<\/code>, NSFont<\/code> etc. are available on macOS. AttributeScopes.UIKitAttributes<\/a> type contains the full list of UIKit attributes and AttributeScopes.AppKitAttributes<\/a> contains the full list of AppKit attributes.<\/p>

Foundation can infer the right type of the attribute to use when we assign the value. The following code will assign UIColor.blue<\/code> as foreground color when UIKit is imported and NSColor.blue<\/code> when AppKit is imported.<\/p>

[…]<\/p>

Note, that when SwiftUI is imported SwiftUI attributes take priority and the resulting attribute value will be Color.blue<\/code> that is defined in the SwiftUI framework.<\/p>

[…]<\/p>

We can even define our own attributes and attribute scopes. This can be useful if we are building a framework or a package or just want to extend AttributedString<\/code> functionality in our app.<\/p><\/blockquote>\n\n

See also: NSAttributedStringBuilder<\/a> (via Kaya Thomas<\/a>).<\/p>\n\n

Previously:<\/p>\n