vercel / vercel/next.js

Redux-observable server side fetching

Open
#15,971 11 comments 13 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

examples good first issue
Dominant language
JavaScript
Stars
142k
Forks
32.5k
Avg merge
2d 14h
Merged PRs (30d)
351

Description

This example is a page that renders information about Star-Wars characters. It fetches new character every 3 seconds having the initial character fetched on a server.

well, I just deployed this example for myself, and wether disabled js or not it doesn't fetches the first sw character's data on a server. Fields just empty with disabled js and the message below is

(was user fetched on server? - false)

Can somebody please fix this and show finally how to implement ssr with redux-observable?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the redux-observable server-side fetching example and trace how the initial Star-Wars character request is handled during server rendering. Reproduce the example with JavaScript disabled and verify that the initial character fields are populated and the server-fetch status reports success.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nextjs, react
Domain
full-stack
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.