Fix type error in Redux Essentials. #3813
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
name: "Fix error in Redux Essentials tutorial"
about: Fixes a type error in the Redux Essentials tutorial
PR Type: Documentation Fix
Does this PR add a new feature, or fix a bug?
This PR fixes a bug in the Redux Essentials Tutorial, fixing issue #3812.
Why should this PR be included?
New users who go through the Redux Essentials tutorial will have code that might not work as expected if this fix is not added.
Checklist
What docs changes are needed to explain this?
See above.
Bug Fixes
What is the current behavior, and the steps to reproduce the issue?
When the user visits the route
/posts/1
or/posts/2
, the not found screen appears.What is the expected behavior?
The post for id
1
or id2
should display.How does this PR fix the problem?
This PR adds a
.toString()
call in a comparison function to fix a type error where the selector was comparing an integer and a string (which will always return false).