Update react-relay to version 0.9.3 🚀

[greenkeeperio-bot]

Hello lovely humans,

react-relay just published its new version 0.9.3.

State	Update :rocket:
Dependency	react-relay
New version	0.9.3
Type	dependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of react-relay. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project :sparkles:

You rock!

:palm_tree:

---

GitHub Release

• Fix issue where containers would forget variables previously set with setVariables, specifically when using array/object variables (closes #1357).
• Add Relay.disableQueryCaching API (closes #754), which may be useful running Relay in a server context.
• Suppress spurious warning when using IGNORE as a rangeBehavior (closes #1337).
• Use a more accurate query name based on current route in RelayQuery.cloneWithRoute (see commit de954992), making logging and analytics that relies on query names more accurate.
• RelayNetworkDebug now prints an estimated request size (see commit b94ba409).
• Preserve type information in callsToGraphQL/callsFromGraphQL, fixing issues with null (closes #1256).
• Fix a subtle ordering issue by writing linked IDs before traversing plural linked fields; this solves a rare edge case where data could be written to the wrong ID given a recursive query (see commit be45692f).
• Expose injectCacheManager on RelayEnvironment (closes #1320).
• Expose Relay.QueryConfig (closes #1279).
• Ensure that instances of GraphQLRange get correctly deserialized (closes #1293).
• Fix a case where tracked nodes would incorrectly trigger a refetch of plural fields with null linked field children (see commit 5c08fd60).
• Make error-handling consistent between 200 status responses with errors attributes and non-200 responses (#1163).
• Warn when producing a diff query involving a client: ID, necessitating the use of a path when a refetchable ID would be preferable in order to produce a correct result (commit 928411df).

---

The new version differs by 729 commits .

• 81b456e Prep for 0.9.3 release
• 5f33d2e Add meeting notes for 2016-08-30 sync
• 22464a1 Rename a file in order to fix TravisCI bustage
• b1d6639 Do not reset variables if outside variable props of type Object are the same
• d01979b Guide Update
• f3b3f93 Add Relay.disableQueryCache static method
• b0d115d Range behaviours: Don't warn when value is IGNORE
• 3a9080b Add recent meeting notes
• 0fc49b2 Include pathToConnection in RANGE_DELETE example on the documentation
• de95499 update concrete node name in cloneWithRoute.
• 1489a8c Reverted commit D3751592
• aad77f0 Relay: Collapse Query Text (+ Cleanup)
• b94ba40 Relay: Print Estimated Request Size
• a5355ba fbsource deploy
• 85e6f1b Test breaking a test

There are 250 commits in total. See the full diff.

---

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? :zap: greenkeeper upgrade}