This PR allows the developers to resolve the Hermes bytecode conversion issue for the Echarts option's function.
Related issue
The default value of "enableParseStringFunction" is "false". It will not affect any original code logic whether the value is "true" or "false". And if the prop is set to "true", any Echarts option's function in string format and starting with the string "function" will be converted to a normal function in the WebView environment dynamically.
Because the function is in string format, the Hermes bytecode conversion will not work. This solution will work as expected in both debug and release modes.
There is also a 'show source' solution from the Hermes official, but from my side, it only works on my Android release environment for now.
Summary
This PR allows the developers to resolve the Hermes bytecode conversion issue for the Echarts option's function. Related issue
The default value of "enableParseStringFunction" is "false". It will not affect any original code logic whether the value is "true" or "false". And if the prop is set to "true", any Echarts option's function in string format and starting with the string "function" will be converted to a normal function in the WebView environment dynamically.
Because the function is in string format, the Hermes bytecode conversion will not work. This solution will work as expected in both debug and release modes.
There is also a 'show source' solution from the Hermes official, but from my side, it only works on my Android release environment for now.
Test Plan
Code:
Running result:
Other notes:
The normal function using 'show source' will also work like before, there is no effect on the origin code logic(even if not using the Hermes engine).