`prepared` doesn't handle async rendering of a component after the fact (i.e. when doing a route change) #15

lhorie · 2017-11-20T22:30:01Z

It requires extra code to make it work in both the hydration and general case and extra user-space checks to ensure requests aren't duplicated

lhorie changed the title ~~prepared doesn't handle rendering of a component after the fact (i.e. when doing a route change)~~ prepared doesn't handle async rendering of a component after the fact (i.e. when doing a route change) Nov 20, 2017

chrisdothtml mentioned this issue May 16, 2019

[fusion-react-async#15] prepared doesn't handle async rendering of a component after the fact (i.e. when doing a route change) fusionjs/fusionjs#285

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

`prepared` doesn't handle async rendering of a component after the fact (i.e. when doing a route change) #15

`prepared` doesn't handle async rendering of a component after the fact (i.e. when doing a route change) #15

lhorie commented Nov 20, 2017

prepared doesn't handle async rendering of a component after the fact (i.e. when doing a route change) #15

prepared doesn't handle async rendering of a component after the fact (i.e. when doing a route change) #15

Comments

lhorie commented Nov 20, 2017

`prepared` doesn't handle async rendering of a component after the fact (i.e. when doing a route change) #15

`prepared` doesn't handle async rendering of a component after the fact (i.e. when doing a route change) #15