Jimmy Jia

We should probably require `eventKey` for ``, then. Care to send in a PR?

I mean just for `` – which won't work without an `eventKey`, unlike the others.

This would be useful for having fields that represent plain JSON objects as well.

It's of very low importance to me as well - it's easy enough to handle this in my own code for now.

On using this pattern a bit, I find that there's a bit of a complication in that naively dehydrating data from Relay on-the-fly causes issues with breaking reference equality, which...

Someone mentioned seeing related performance issues with repeatedly instantiating Moment.js objects on the component. Would it be possible to re-open this issue? I understand that this is unlikely to be...

Here's an additional problem. Suppose I have a field that deserializes into a non-scalar type. If I use this field in multiple nested components, I have a choice of either...

JSON "just works" even with Relay Modern w/graphql-type-json, BTW.

> In our schema most fields are non-nullable Do you mean "nullable" here?

This would be pretty nice to have. In the context of object-oriented APIs, it's pretty nice to have abstract classes where consumers have to implement specific methods to get certain...