Refactor dataForChild on DocumentType.Mutation to use new bound funct…

[baerrach]

Attempt at fixing #725

dataForChild previously returned a new function for type DocumentType.Mutation
causing React shallowEqual render optimizations to fail.

Refactored the mutation specific code into its own method with a binding to
'this' in the constructor.

Haven't create a test case for this as all the tests render nulls, and this only shows up in real use on multiple renders. I'm not enough of an expert on React and testing to know how to do this properly.

TODO:

• If this PR is a new feature, reference an issue where a consensus about the design was reached (not necessary for small changes)
• Make sure all of the significant new logic is covered by tests
• Rebase your changes on master so that they can be merged easily
• Make sure all tests and linter rules pass
• Update CHANGELOG.md with your change
• If this was a change that affects the external API, update the docs and post a link to the PR in the discussion
• If this was a change that affects GitHunt-React, update GitHunt-React and post a link to the PR in the discussion

[helfer]

Thanks @baerrach, I think this is great! I'd be okay with merging this without a test, but if @jbaxleyiii has some ideas for testing, it would be great to add one. I assume testing for re-renders is a solved problem, so there should be some prior art. If not, we should document it and write a blog post about it 😁

[helfer]

Thanks @baerrach, I think this is great! I'd be okay with merging this without a test, but if @jbaxleyiii has some ideas for testing, it would be great to add one. I assume testing for re-renders is a solved problem, so there should be some prior art. If not, we should document it and write a blog post about it 😁

[baerrach]

Yes, I'm all for writing tests with PRs.
And I need to know how to do this for my own work. So I'm keen to learn.

[jbaxleyiii]

I'd be happy to show you how to test this! I'm out of town starting tonight so it won't be until Sunday though

…

On Wed, Jun 14, 2017, 7:51 PM Barrie Treloar ***@***.***> wrote: Yes, I'm all for writing tests with PRs. And I need to know how to do this for my own work. So I'm keen to learn. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#772 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEvMsEpU22xWPM2GZl18Gnh9Cskx-QLZks5sEHHpgaJpZM4N4e1P> .

[baerrach]

I'm in no rush.

I also just found How to Fork and Patch NPM Modules so I can stop manually editing files in node_modules.

[derek-duncan]

@baerrach thanks for tackling this one. I just wanted to note that all of the functions in the data object create a new reference each render. Should we include these in this PR as well?

Functions in data response for queries.

data.refetch(variables)
data.fetchMore(options)
data.subscribeToMore(options)
data.startPolling(interval)
data.stopPolling()
data.updateQuery(updaterFn)

[baerrach]

Yes, its a can of worms that needs looking at thoroughly.
Its probably not my area of expertise those, so if you can find someone who has the time and knowledge it would be best to get them to look over the code base with that in mind.

First step might be to write tests to make sure things aren't re-rendering unnecessarily, then that will give people a list of things to work on.

With a set of guidelines in place on how to resolve the typical issues other people should be able to chip in and fix it up bit by bit.