David Furman

Results 14 comments of David Furman

@stephencelis Just checking in on this to see if there's any action you'd need from me here for this PR to be accepted. Ultimately, this would help devs with a...

To those who it may help, I've created some extension properties to make working with `GraphQLNullable` a bit easier with property chaining, letting you quickly adjust pre Apollo 1.0 code...

This seems related to an issue brought up here: https://twitter.com/b3ll/status/1193747288302075906?s=20 Additionally, a more fleshed out fix (see: hack) is here: https://defagos.github.io/swiftui_collection_part3/ There's also a radar issue opened for this: https://openradar.appspot.com/FB8176223

@Matejkob Just a heads up, after my other two PRs get in, I’ll likely take another look at self-reviewing this PR with a bit of a fresh take having given...

@Matejkob Alrighty I think I've simplified my approach as much as I'm able to right now. It's still quite a bit of code, so no rush on getting to this,...

@arennow I think you're right about a solution having to revolve around the use of `Any` for storage. I'm not sure that we need to be concerned with protocol conformances...

@arennow Thanks for the clarification! I see what you mean now. Yeah, being able to use generic constraints could help eliminate some situations where devs need to cast from `Any`....

Our backend has used "Void" to represent Null values in our schema. ```json { "kind": "SCALAR", "name": "Void", "description": "Represents NULL values", "fields": null, "inputFields": null, "interfaces": null, "enumValues": null,...

```swift public typealias Void = Swift.Void extension Void: CustomScalarType {} // Non-nominal type 'Void' cannot be extended ``` This is what I run into when trying to follow that path....

Yeah I appreciate the quick responses and totally understand that this is probably a tricky edge case! I do understand there's some [wariness about adding additional configuration options](https://github.com/apollographql/apollo-ios/issues/2598#issuecomment-1289608141) that'd complicate...