| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
chore: clear MoonBit toolchain-upgrade warnings workspace-wide The moonc 0.10.14 upgrade introduced new lint categories that fired ~31k warnings across the workspace. All own-code warnings are now eliminated on native and wasm-gc (moon check --warn-list +73 reports 0): - unnecessary_annotation: drop redundant @pkg.Type:: / Type:: qualifiers on constructor and variant references - test_unqualified_package: qualify cross-package types in black-box tests with the package alias (e.g. @renderer.Renderer) - implicit_impl_as_method: make the deprecated implicit trait-method promotions explicit with #doc(hidden) extend declarations collected in per-package extends_*.mbt files (trait-family split for moui/core). Promotions keep working; the generated .mbti interface is unchanged, so API-surface budgets and public declaration counts stay at baseline. - unused_package: drop unused moon.pkg imports; move test-only imports into for "test" / for "wbtest" blocks (moui/backend/common keeps its architecture-mandated core import with a targeted warnings = "-unused_package" opt-out) - deprecated APIs: Array::new -> Array, sub/view -> exact_view - misc: unused variables (_self), reserved keyword (move -> move_event), unused fields, unused type declarations, dead functions Also updates checks/source-file-policy.json ratchets (shrunk files ratchet down, tests grown by required qualification ratchet up) and the maintenance-baseline line budget for the reformatted tool catalog. examples/momark and examples/deepseek_harness_desktop carry the same cleanup as local submodule commits (not pushed). Known pre-existing issue (not caused by this change): the local .mooncakes cache holds bobzhang/pdflite@0.1.38 (a yanked package superseded by moonbitlang/pdflite), whose rijndael dependency uses toolchain-removed syntax (@strconv.from_str, fnalias). Root-level moon check and check-generated-interfaces.mjs fail on those third-party sources until the dependency is migrated. | 5 天前 | |
feat(website): add live demo links and corresponding tests for showcases | 1 个月前 | |
fix(playground): include moui_web_renderer in in-browser compiler assets The fixed Runner (compiler-worker.js RUNNER_SOURCE) imports wzzc-dev/moui_web_renderer as @webgpu_adapter, but the asset closure generator only collected ALLOWED_IMPORTS plus moui/runtime and moui/backend/web. The in-browser compile of any project then failed with "Package asset is unavailable for wzzc-dev/moui_web_renderer". - generate-playground-assets.mjs: add moui_web_renderer to the package closure so manifest.packages contains its .mi/.core entries. - compiler-worker.js: add moui_web_renderer to the linkCore roots so its core is fetched; without it linking failed with Key_not_found for $_M0FP210wzzc_2ddev19moui__web__renderer9from__env. The registry index also needed (via proxy) before asset generation could resolve the workspace dependency graph. Verified: regenerated dist/playground passes scripts/test-playground-assets.mjs; a headless-browser compile of the default lesson reports status success and the preview iframe renders "Hello, MoUI! Count: 0" (871 non-white pixels). | 1 个月前 | |
Update dependencies and refactor editor scroll handling - Updated MoUI dependencies to version 0.2.0 for improved features and stability. - Refactored editor scroll handling in editor_view.mbt to use Point for scroll state. - Removed unused state import in moon.pkg. - Adjusted pkg.generated.mbti to reflect changes in scroll state type. - Modified playground_model.mbt to accommodate new scroll handling logic. - Updated compiler-worker.js to use the new moui_web_renderer instead of webgpu_adapter. - Changed script imports in index.html files to reference the updated renderer. | 1 个月前 |