This repository was archived by the owner on Dec 15, 2021. It is now read-only.
Open
Conversation
- Treating this as a sub-router. - Cleanup some state as it's a bit hacked together given it may not fully be available. - Tweak folder structure a bit.
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
A very generic 30m example for how to use a
react-router-domanduseContextwith some API calls./users/:userIdand/books/:bookIdwould work just fine with a slightly amended parent router.location.state.deletedUser(eg. a nice-to-have, but not a requirement if the user does lose this location state). Similarly, checks if the user can still be restored incase thelocation.statehas leaked..