[weex] Adjust the weex platform entry file to fit the new weex runtime #6620
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.
Remove the
new Function
hack for V8Remove the
callFunctionNative
method and thecompileBundle
API which is provided by modified V8.In order to maintain the consistency of the js engine, Weex also uses JSC on Android. The legacy hack for V8 engine should be removed.
Move shared APIs to Weex runtime
Modules and components should be registered in weex runtime, not in each front-end frameworks. The
registerModules
,registerComponents
,weex.supports
andweex.requireModule
APIs is moved toWeex runtime which is in the https://github.com/apache/incubator-weex .
Use
document
instead ofrenderer
Using
document
is more standard than usingrenderer
. ThecreateElement
API support to create customWeexElement
now.Test cases
Weex's test cases have also been adjusted to fit the new
weex-js-runtime
architecture.