Frederick Pietschmann

I updated - layerset_availability.plist - name_aliases_strings.txt - name_availability.plist - symbol_names.txt - symbol_previews.txt from / using the SF Symbols 4 Beta app and regenerated the code. Fortunately, everything went fine, so...

Okay, there is one minor issue: In the `localization_availability.plist`, there is an entry `square.3.layers.3d.down.forward.slash.rtl`, but not an entry for the "base variant" `square.3.layers.3d.down.forward.slash`. In the SF Symbols app, therefore, the...

I pushed a new commit with the new symbol restrictions file from Xcode 14 Beta. Thanks @StevenMagdy for documenting the information where to find it (via #108). Interestingly, the Xbox...

> To avoid conflicts, let's wait until #106 is merged before implementing this. Implementing this fix is also a good first issue, if someone is interested. As #106 is now...

I have now fixed the issue mentioned above myself.

The 4.0.0 release is now available: https://github.com/SFSafeSymbols/SFSafeSymbols/releases/tag/4.0.0

@StevenMagdy Thanks for the PR! Unfortunately, the CI is a real mess currently. In The Xcode 14 Beta 5 Release Notes, it said that the simulator issue would be fixed,...

@narwahle Thanks for raising this issue! As I wrote in https://github.com/SFSafeSymbols/SFSafeSymbols/issues/75, I feel like we can't make sensible use of the category information. But now, that you raise this issue,...

@narwahle Thanks for the reply! Then I suggest we offer a `is(category:)` interface for `SFSymbol` similar to the `has(localization:` interface. For the purpose of getting an array of symbols of...

@knothed That's also an option – then, the association between symbol raw value and symbol localizations and symbol categories would be made on initialization with `SFSymbol(rawValue: "...")`. As per @StevenMagdy's...