This repository has been archived by the owner on May 7, 2019. It is now read-only.
Pager component is having js warnings after react upgrade #202
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
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.
This is a fix for the following warning:
This error is coming from every place with the Pager (Task Scheduler, Roles, Users...).
The most common reason is that application tries to modify the state for the unmounted component AND/OR for the component that is already mounted but rendered with nothing (like in our case).
To fix it, we just need to make sure Pager returns something while waiting for data, i.e. empty
div. Once data prepared it will re-draw Pager component with all its structure.Fixes #195