Skip to content
This repository was archived by the owner on May 4, 2019. It is now read-only.

Commit f42258a

Browse files
author
mattjstar
committed
quick edits
1 parent 89b530a commit f42258a

File tree

1 file changed

+5
-7
lines changed

1 file changed

+5
-7
lines changed

_drafts/react-reflux-to-redux.markdown

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
layout: post
3-
title: React Flux (Reflux) to Redux Tutorial
3+
title: React Tutorial - From Flux (Reflux) to Redux
44
author: Matt Star
55
summary:
66
image: http://res.cloudinary.com/wework/image/upload/s--xpIlilub--/c_scale,q_jpegmini:1,w_1000/v1443207604/engineering/shutterstock_294201896.jpg
@@ -25,7 +25,7 @@ Going from a state where most of the location filters are hidden, with a link th
2525

2626
![Filters Expanded](http://res.cloudinary.com/wework/image/upload/s--sM1ilgkF--/fl_progressive,q_jpegmini:1/v1443360347/engineering/fewer_filters.jpg)
2727

28-
### The old way...jquery:
28+
### jquery - the old standby:
2929

3030
In an *imperative* example using jquery you could have a listener to that specific link, and when it's clicked have it toggle the hidden filters container:
3131

@@ -41,7 +41,7 @@ How can we do better???
4141

4242
Let's now look at the more *declarative* example with our initial Reflux implementation.
4343

44-
### The new kid on the block...Reflux:
44+
### Reflux - the first attempt:
4545

4646
What if we had access to a boolean that told us whether we should show or hide the hidden filters container? Our React components would listen to that boolean so it would know what to display (...*declarative*), then our link component would simply dispatch an action that would toggle that boolean when clicked.
4747

@@ -168,7 +168,7 @@ I know this might seem like overkill essentially replacing 3 lines of jquery and
168168
But this tutorial isn't about why you should use React. What about Reflux???
169169

170170

171-
### That new hotness...Redux:
171+
### Redux - Finally:
172172

173173
When you start building larger production level applications that require many types of stores and a more complex data model, reflux can start to feel a little bloated (TERRIBLE PUN). Redux is a natural successor to reflux (and other flux patterns in general).
174174

@@ -588,9 +588,7 @@ export default connect(
588588

589589
## EXAMPLE 3: Filtering that Fetched Data
590590

591-
What if we want to filter any of our existing data? For that you use [reselect](https://rackt.github.io/redux/docs/recipes/ComputingDerivedData.html).
592-
593-
Reselect allows you to create memoized selectors that only update when the sections of the store that it is listening to are updated.
591+
What if we want to filter any of our existing data? For that you use [reselect](https://rackt.github.io/redux/docs/recipes/ComputingDerivedData.html). Reselect allows you to create memoized selectors that only update when the sections of the store that it is listening to are updated.
594592

595593
In the example of filtering locations:
596594

0 commit comments

Comments
 (0)