Reorder categories in the directory #462
Open
Conversation
This file contains 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
|
Commit |
|
|
||
| // According to the type definition, `navigate` returns a promise, but in | ||
| // practice it does not. | ||
| // eslint-disable-next-line @typescript-eslint/no-floating-promises | ||
| navigate('/explore', { replace: true }); | ||
| navigate('/explore', { replace: true, state: { isFromCategory: true } }); |
There was a problem hiding this comment.
I'm not sure I follow why this is necessary. We can change the ordering by dispatching setOrder?
There was a problem hiding this comment.
The explore page should always be on latest ordering, how would I know if the explore page was rendered by it being navigated to via the category page or not.
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.
Closes #2964