mirror
/
front-end-interview-handbook
mirror of https://github.com/yangshun/front-end-interview-handbook.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[JS] Code organization typo fix (#192)

This commit is contained in:
Chris Diana 2019-06-01 11:35:55 -06:00 committed by Yangshun Tay
parent 9e40dca67a
commit 135762c097
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
questions/javascript-questions.md
View File

@ -280,7 +280,7 @@ console.log(double); // [2, 4, 6]
### How do you organize your code? (module pattern, classical inheritance?) ### How do you organize your code? (module pattern, classical inheritance?)
In the past, I used Backbone for my models which encourages a more OOP approach, creating Backbone models and attaching methods to them. In the past, I've used Backbone for my models which encourages a more OOP approach, creating Backbone models and attaching methods to them.
The module pattern is still great, but these days, I use React/Redux which utilize a single-directional data flow based on Flux architecture. I would represent my app's models using plain objects and write utility pure functions to manipulate these objects. State is manipulated using actions and reducers like in any other Redux application. The module pattern is still great, but these days, I use React/Redux which utilize a single-directional data flow based on Flux architecture. I would represent my app's models using plain objects and write utility pure functions to manipulate these objects. State is manipulated using actions and reducers like in any other Redux application.