fix(backend): ensure currentAppRecord is defined when backend handli… #2070
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.
…ng components events emitted from Vue. (fix #1770)
Description
I have noticed that there are some issues caused by the reason that
currentAppRecord
is not defined (but it is used when some hooks such asCOMPONENT_ADDED
are called). Typical issues are #1770 and #1711. And there is good case analysis.I had same issue when I developed a Micro Frontends project which contains both Vue2 and Vue3 app instance. And I found that
selectApp function
is almost a synchronous function. So I just change the order of code execution increateAppRecord function
then errors disappeared.@yyx990803 吐槽一下,这个二十几k星项目的文档还有很大的提升空间。
Additional context
What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123
).