Refreshing faster user reaction UI status for content #42
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.
PR Checklist
Please check all that apply to this PR using "x":
PR Type
What kind of change does this PR introduce?
Fixes
Issue Number: #1
What is the current behavior?
User reaction status to content is not updated until the scheduler is executed
What is the new behavior?
Reactions amount is updated accordingly on the UI
Other information
After a successful API call to react, the code to refresh the UI is called with an updated object. After that, the regular scheduled task is again created. This way, app refreshes the UI status before getting the remote data, but using the reaction request response as the reason to update the status. This makes it feel faster, as the UI is refreshed immediately without having to make a new request.