Rene Eichhorn

First of all thanks for the write up! I agree that having replication "early" on would be a big plus for bevy. Not sure if this is PR is still...

Found out that this can be solved by adding the key prop to the Route component. `props.key = this.state.selfPathname` before `React.createElement(...)` There is no way to pass a unique key...

It has one, I'm just using the example given in the repository @vifird

The main issue is that without the key prop react won't understand what is a new component and what not. Therefore it will just think every route is just the...

I will give you an example: Imagine a /product/:id route that uses the Product component. The product component uses componentDidMount to recieve data from the server. (as suggested by react...

I think this issue goes beyond stabilizing the id across suspension on client-side updates. This also affects SSR and client hydration. I recently ran into an issue where the id...

> I've read through it and I don't understand what behavior you want. Can you please describe what you want to happen when the button is pressed? My expectations from...

The reason we want to have Suspense boundaries around each product is because in [our architecture](https://engineering.zalando.com/posts/2021/09/micro-frontends-part2.html) the Product component only retrieves its UUID as a prop and then fetches its...

For us it is really just an empty hole although I'd also think a glimmering placeholder would look even better but that's not what we want to have for the...

I think this should be reopened as it still is an issue. The workaround from @cjies works but that's certainly not how it should be. Wrapping components is a very...