iam4x/isomorphic-flux-boilerplate

Question: Notification component implementation

Open

#123 opened on Oct 9, 2015

View on GitHub
 (5 comments) (0 reactions) (0 assignees)JavaScript (115 forks)github user discovery
help wantedquestion

Repository metrics

Stars
 (791 stars)
PR merge metrics
 (PR metrics pending)

Description

Hi,

First of all, thanks for this boilerplate! It's awesome!

I've been playing with this and tried to implement a component that I created for notifications. I set this version using the component: https://isomorphic-react-app.herokuapp.com/

You can see the notifications when:

  • Delete a user
  • Add a user

When adding a user, sometimes it will fail and display a error notification and sometimes it will be success, just for simulation purpose. In case of fail, there is a button where the idea is re-do the action.

My concerns and goals here are:

As I'm new to Flux implementations, my question here is about the structure of the store and actions, if you guys think it's ok. The repo is here: https://github.com/igorprado/isomorphic-react-app

Thanks!

Contributor guide

Research direction
Review the notification store and action implementations in the linked repo. Focus on the Flux data flow: actions dispatch to store, store emits changes, components listen. Ensure that the notification store properly listens to actions and that the component re renders on store changes.
Tech stack
javascriptreact
Domain
frontend
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ReactFlux
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65