alidcast

Personally, I've always preferred frameworks over boilerplates / starter-kits. The beauty of a framework done right, is that it's code you don't have to think about, see, or maintain. This...

what's the status of the RN integration?

fyi this is working for me in monorepo (initially had wrong config, so noticed this issue and figured I'd let you know it does work. im using latest expo/RN/metro) ```...

@FredyC the data prop is also useful in case you don't want to update the respective queries but still need to know the result of the mutation. this use case...

i guess another approach is to remove the optimistic response for the mutations that need the actual result (and then just wait for mutation to resolve like described above)

yeah but it can check if the query itself is the same (the inline syntax works with relay for example) it's unintuitive that the same query would cause a rerender...

for context i'm totally fine with declaring the `gql` tag outside the function as its own variable but while testing out a query this caught me off guard, so I...

yea but since the `getMarkupFromTree` also renders the markup, if it fails then you can't render the app. ideally graphql errors wouldn't cause it to fail, that's how I've usually...

@trojanowski yea it'd be great if react-apollo-hooks implementation could be compatible so that we can handle errors in the app itself (rather than having to deal with the error /...

so would it be OK to remove this snippet here? https://github.com/trojanowski/react-apollo-hooks/blob/master/src/getMarkupFromTree.tsx#L32-L34 and let end user decide how they want to handle non-suspense errors