v0.10.0

• Breaking: Move from React Router to rrtr

v0.9.5

• Feature: Support non-scalar Relay route parameters from prepareParams

v0.9.4

• Bugfix: Pass the component key to the wrapped createElement function in <RouteContainer>

v0.9.3

• Bugfix: Fix forwarding props into route components

v0.9.2

• Minor: Fix a publishing error in v0.9.1

v0.9.1

• Feature: Add support for named components, courtesy @denvned

v0.9.0

• Breaking: Support React Router v2.x instead of v1.x

v0.8.0

This is a relatively big release with significant breaking API changes.

The main change in this release is to move to a new top-level API made possible by new features in React Router. Now, instead of specifying createElement, you active the Relay integration by using <RelayRouter> or <RelayRoutingContext> as appropriate. This change lets us do a couple of new things:

• We now support async components resolved via getComponent
• We have a way to pass additional props like forceFetch to the Relay.RootContainer

There are a couple of smaller fixes included as well:

• We preserve the signature of query functions, which fixes a bug when using non-shorthand queries against Relay v0.5.0
• We now pass through readyState to the renderFetched handler as well

v0.7.0

This updates the dependency versions for Relay and React Router.

v0.6.2

Thanks to @josephsavona, we now have support for an additional prepareParams property on routes. Similarly to prepareVariables on a Relay container, prepareParams allows you to modify the params used for the Relay route. For example, you can use prepareParams to convert URL and query parameters from strings, and to initialize missing params with default values.

We've also bumped the React dependency from v0.14.0-rc1 to the final v0.14.0 release.