v0.6.1

In some cases, the previous logic for generating unique query names based on referential equality of routes would break due to the route objects changing. This would lead to routes getting stuck in renderLoading forever due to changes in the generated unique query names. This release adds support for explicitly named routes, which allows us to match query names even when the route objects break referential equality.

v0.6.0

• Add support for Relay route parameters coming from location state
• Only update the Relay route on actual location changes

v0.5.0

This brings the package up-to-date with the recent changes in each of the major dependency packages.

v0.4.5

This release adds hasVariable to RouteAggregator, which provides support for future releases of Relay that require this method on containers.

v0.4.4

This release fixes the React Router peer dependency. We're only compatible with React Router 1.0.0-beta3 for now.

v0.4.3

• Match the new requirements for Relay containers in v0.2.1
• Support using the same query for multiple routes

v0.4.2

This adds back support for the case where a route component's parent calls React.cloneElement to inject additional props into the route component by passing through props into the wrapped component from containers.

Fix dependencies

Added a missing babel-runtime dependency.

Refactored internals and new API

We're now react-router-relay (instead of relay-nested-routes)!

@taion did some great refactoring with help from @cpojer to simplify the library while making it support more use cases.

Nested routes and queries are still aggregated up to a single Relay.RootContainer and dispatched in one go for batching and server side rendering, but now it's possible to provide RootContainer-esque functions on a per route basis like renderLoading, renderFetched, and renderFailed, in order to customize the experience for your app.

Thank you @taion and @cpojer for all your hard work!