pass init data to Link when available and avoid a server request about react-router

[ryanflorence]

Great question.

The store in that example keeps the data cached, so it doesn't make new server requests for data it already fetched.

I have found in ember, (which typically works like {{#link-to "user" userData}}) that devs think their user route works if you land there, but it doesn't if their model hook is broken so it only works when you start one route above (the route that gets the data).

In other words:

1. Land at /
2. Data is fetched
3. User clicks link that passes data in
4. Route renders perfectly, model hook ignored

Now consider:

1. Land at /users/123
2. Data has not fetched yet from the parent route
3. Model hook doesn't work
4. Route is broken.

In my experience this happens a lot in ember, so I designed this router to just pass the parameters and not data objects so that your code always runs the same way (instead of two code paths). It is the store's job to avoid server requests, not the incidental hierarchy of your components and their data.

[ioRekz]

Ok thank you. That make sense!