[Data Explorer] Add lazy loading to enable all the services for canvas #4432
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.
Description
Currently the createCanvas function is indeed being called only once when the Discover plugin is being set up. The return value of this function (a React Element) is then saved in the ui object of the registered view and this same React Element is used every time the DataExplorerApp is rendered. Because React Elements are plain objects and not functions, they don't get re-evaluated or re-rendered. This PR is just a minor adds-up to unblock implementation table vis by adding lazy load. This will render the actual component in place of the fallback when the component becomes available.
Issues Resolved
#4419
Screenshot