Will Lumley

This PR introduces functionality that allows for the set of unit tests to be ran on the three platforms that FaviconFinder supports: iOS, macOS, and Linux.

Thoughts on adding "in-built" support for external data sources (ie .`FlagValueSource`s?)

2

I feel like it'd be neat to have native / in-library support for other types of data storage types. Such as FirebaseRemote Config, Launch Darkly, or even GRDB, etc. If...

Documentation on how to setup the `FlagValueSource` as a shared `UserDefaults` from the "Settings" app

4

In the documentation it is stated that we recommend that the view/Vexillographer be contained in its own app. This requires the user to setup an App Group, and then set...

Updated `AppFlags.swift` to `AppFlags.self` in Vexillographer.md

1

### 📒 Description I noticed that in the [DocC](https://vexil.unsignedapps.com/documentation/vexillographer/) that instead of `AppFlags.self` there was `AppFlags.swift`. This is just a tiny PR to correct that. ### 🔍 Detailed Design N/A...

While there is barebones unit test coverage, we need to have a much higher degree of coverage. This includes unit tests for each individual Finder, and ensure that all extension...

To enhance the performance and reduce redundant network requests, I propose adding a caching mechanism for favicons. This would allow FaviconFinder to store previously fetched favicon images locally (in memory...

**Description** As a future enhancement, I would like to add a feature that simplifies the process of inserting a favicon into apps. This would involve creating a custom view that...

**Description** To extend the flexibility of FaviconFinder, we would like to allow users to create their own custom FaviconFinder implementations. This would enable users to define new ways of retrieving...

This PR adds `Codable` conformance to the `SFSymbol` class. ## 🔍 Rationale In many modern Swift apps, we pass symbols through persistence layers (UserDefaults, JSON, CloudKit, etc.) or across thread...