feat(weex): adjust framework entry APIs and add flow annotations #7272
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.
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
Other information:
Remove legacy framework APIs
Remove the
init
,reset
,getRoot
andreceiveTasks
APIs, which are already implemented in the new version ofweex-js-runtime
.Moreover, the deprecated timer APIs should also be removed when they were supported by native render engines (C++ timers).
No longer execute the js code at front-end
Use
createInstanceContext
instead ofcreateInstance
to create the Vue module instance for each page. The Vue framework only needs to prepare the instance context and no longer execute the js code. The js code will be executed by native render engines.Flow type declarations
Add more reliable flow type declarations of Weex instance APIs and DOM APIs, and add type annotations for the entry file.