-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wasm] simplify startup configuration #61072
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
@steveisok we need a way to test changes like this in pr without directly fiddling with the yml. I think we should probably turn back on the interpreter lane until we have a way to trigger this cc @marek-safar |
I don't have a problem if you want to enable the interp lane until there's an option to manually trigger everything. Remove runtime/eng/pipelines/runtime.yml Line 296 in ec12194
|
* added Module.onConfigLoaded callback * added Module.onDotNetReady replacing MonoConfig.loaded_cb * removed loaded_cb, assembly_list, runtime_assets, runtime_asset_sources from MonoConfig * simplified all sample and test projects * renamed no_global_exports to disableDotNet6Compatibility * implement default Module.preInit and Module.onRuntimeInitialized which could be overriden by user code (like Blazor)
78c1c10
to
5e4d4e8
Compare
Module.configSrc
- to configure path toMonoConfig
json fileModule.onConfigLoaded
callbackModule.onDotNetReady
replacingMonoConfig.loaded_cb
loaded_cb
,assembly_list
,runtime_assets
,runtime_asset_sources
fromMonoConfig
Module.no_global_exports
toModule.disableDotNet6Compatibility
Module.preInit
andModule.onRuntimeInitialized
which could be overridden by user code (like Blazor)