Server-side rendering via renderToString?
- Dominant language
- JavaScript
- Stars
- 101
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I was just looking through a few Flux implementations and stumbled upon fluxify. One major problem I have with Flux is the difficulty of building isomorphic apps. With React (no Flux) it's quite easy because you can pass the props to `renderToString` and set the state directly on the component.
But with examples like [Chat app](https://github.com/facebook/flux/blob/master/examples/flux-chat/js/components/ThreadSection.react.js) you don't store the data on components; it's delegated to the stores. As a result, I cannot generate a component's markup since I can't pass the data via props anymore.
Does fluxify have a way around this problem?
Thanks.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing fluxify's store and component APIs, then compare their data flow with React's renderToString usage and the linked Flux chat example. The issue does not name a repository file or test; done would require a decided, documented way to render store-backed components for isomorphic apps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100