Update testing guide #4819
Open
Update testing guide #4819
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
✅ Deploy Preview for redux-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
EskiMojo14
force-pushed
the
test-docs-update
branch
from
6a73b5f to
f111051
Compare
EskiMojo14
force-pushed
the
test-docs-update
branch
from
1f76ce4 to
4704652
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: 📖 New/Updated Documentation Content
about: Adding a new docs page, or updating content in an existing docs page
PR Type
Does this PR add a new page, or update an existing page? Existing
Checklist
What docs page is being added or updated?
For Updating Existing Content
What updates should be made to the page?
user-eventinstead offireEventPreloadedStatetype properly instead of assumingPartial<RootState>Do these updates change any of the assumptions or target audience? If so, how do they change?
Updates recommendations for newer technology available (Browser testing avoids the need for JSDOM etc)