Jesse Farsong

@designatednerd any updates on this? Not being able to exhaustively switch over union types adds a fair amount of fragility that's hard to ignore.

It works more easily in a test case scenario where you might know it's being called. (Although even then, its unfortunate to have to expose such knowledge of the implementation...

Here's a quick slimmed-down example I threw together: https://github.com/solidcell/iOSSandbox/tree/realm-async-testing There's just one test in there, which highlights the issue. The link to `testNotificationSentInitially` which you provided doesn't really address the...

Sounds good, thanks for the update. I just figured I'd throw the idea out there to see what others thought, at the very least.

Yea I've already read the migration guide. The easiest way I've found to get a first pass which compiles, and sort of works is to not use a `typealias` directly...

If I don't conform to `SelectionSetEntityValue`, I get this error: Using `AnyHashable` instead of `Any` as the value didn't change anything (either better or worse), so I'll leave it as...

For anyone else running into this, I have two solutions: Maestro ``` - launchApp: appId: "com.apple.Preferences" - tapOn: "Passwords" - inputText: "a" # anything works here as the password -...

@calvincestari Thanks for the example. > a custom scalar named JSON of type [String: AnyHashable] Maybe I'm misunderstanding this, but that's not quite true. It's still a _wrapper_ around `[String:...