FOUR-8352 Importing node components async #1618
Closed
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.
Issue & Reproduction Steps
Expected behavior:
Components should be imported async when needed. For example.
If we are going to use the "Signal End Event" and put it in the paper, as soon as the user puts the icon in the paper, we will trigger an AJAX Call (done automatically by Webpack) to import that component async to alleviate the final build result, resulting in the final build having the necessary to run modeler and "chunks" to be loaded async when needed.
Actual behavior:
Currently not doing anything async
Solution
How to Test
Test the steps above
Related Tickets & Packages
Code Review Checklist