Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server-side rendering #48

Open
1 of 5 tasks
TehShrike opened this issue Oct 23, 2015 · 3 comments
Open
1 of 5 tasks

Server-side rendering #48

TehShrike opened this issue Oct 23, 2015 · 3 comments

Comments

@TehShrike
Copy link
Owner

  • ability to load resolve data from a global instead of fetching the data remotely (pull request Add in a global option to bypass the resolve #49)
  • ability to get the resolve data from a state transition
  • another module to wrap renderers and collect the domApis
  • another module to add click handlers to every hash link in the dom, that could be easily composed with state change success events
  • document all of the above, replacing the "server-side rendering" section in the readme

Pull requests accomplishing any of the above bits should be opened against the server-side-rendering branch.

@saibotsivad
Copy link
Collaborator

Oooh, fancy!

@TehShrike
Copy link
Owner Author

One down!

@TehShrike
Copy link
Owner Author

I created a new server-side-rendering branch where we can work on this without releasing bits piecemeal into master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants