-
Notifications
You must be signed in to change notification settings - Fork 0
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
23 add redux #39
23 add redux #39
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #39 +/- ##
=========================================
+ Coverage 52.38% 60.78% +8.4%
=========================================
Files 7 8 +1
Lines 42 51 +9
Branches 8 10 +2
=========================================
+ Hits 22 31 +9
Misses 12 12
Partials 8 8
Continue to review full report at Codecov.
|
Now would be a good time to mention that both of these extension dev tools are super helpful: Redux dev tools - these are particularly awesome if you dip in to the front end at some point check them out boi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work, all looks good as far as I can see
import Landing from '../Landing/Landing'; | ||
import './App.css'; | ||
|
||
// if in development, enable redux dev tools | ||
const enhancer = | ||
process.env.NODE_ENV === 'development' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will need to add some config files or somethin later on. good reminder of that
Decided to go with a modified ducks structure for now described in this article.
We can go over more the structure, but it's basically a tighter coupling of the different action types, action creators, and reducers that will control the application's state. Or at least keeping them together in the same files for the most part, rather than having a few different directories. I like the way this seems, but we'll see how it plays out.
Also, while doing this, I ran in to a really weird Jest caching bug that was showing old non-existent files in my coverage reports. I resolved it by following instructions here and manually clearing my Jest cache but hopefully this doesn't happen again 🤞