Chris Drackett

@barbalex have you tried with a different fetch policy? are you using data off `data` or out of the store?

and all the things coming down have a typename and ID? sorry, trying to be helpful :)

I haven't run into his myself, but your description makes sense. I would agree that solution 2 is the most desirable way forward with this.

I wonder if the `ModelSelector` and `selectFrom`bits from each model could be moved into a file that is loaded first so that these are usable in any model file?

This might not be helpful, but the way we handle this is having a `isDeleted` flag on the record in question. In this case the `deleteUser` mutation would return the...

@RXminuS Maybe we should open up a new issue or project to cover the exploratory work around this idea? I think its good to keep this issue small and focused,...

I'm guessing this is due to a bug related to the new naming that @beepsoft worked on. I would start looking at the changes in this PR first: https://github.com/mobxjs/mst-gql/pull/155 Who...

agree, if we want a descriptive name we are pretty good right now, IMO.

note, I just saw the note on this here: https://github.com/graphql-nexus/nexus/pull/1261#issue-455004240 and stopped searching :)

also running into this. Tomorrow I'm going to look into keeping our server in the same repo, but pulling it out from being a workspace, if that is even possible.