-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
MyLand refresh/navigation fix #333
Conversation
Sure! Each type of network request - A) fetching my land; B) fetching land for sale; C) fetching account funding plus approval should have a name for that network request, and then when it it starts we save to redux that network request with name The relevant one here would be the my land request. Although going too far down this path might not be the best use of time because of the React Suspense discussion here #197 Does that clarify it, or should I go into more detail? |
Oh, I see, something like this? { type: 'FETCH_POSTS_REQUEST' }
{ type: 'FETCH_POSTS_FAILURE', error: 'Oops' }
{ type: 'FETCH_POSTS_SUCCESS', response: { ... } } Extracted from redux doc. |
Yep, exactly |
@marcelomorgado I know there were a couple issues being tracked in issue #267 . Have some of them since become obsolete? Just checking whether this PR indeed closes all of them. |
This PR is addressing:
|
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.
@marcelomorgado Great work!
Awesome, this is a big improvement!! |
…itlabs/tasit into feature/myassets-refresh-fix
…itlabs/tasit into feature/myassets-refresh-fix
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.
@marcelomorgado This is looking great! It's very impressive how quickly you turned these changes around.
Issue link
#267
Auto-close the issue?
Closes #267
Types of changes
Bug fix (non-breaking change that fixes an issue)
New feature (non-breaking change that adds functionality)
Notes
Could you tell more about your last comment on the issue?