Conversation
|
Thanks for a valuable contribution. A few suggestions before we move any further:
Also, we should probably consider deduplicating reports from Ruff, mpy-cross and Pyright |
|
Thanks for the initial review, I agree with most of the points above. A few follow ups
VsCode uses Problems, that or Diagnostics seems best.
Agree, do you have an example how to trigger such a message?
I'll need to look into that. In the stubs playground client I remember I needed to do extra work on the merging and sorting of the rather poor suggestions from code mirrors python and the ones from pylance.
That was the intent, to avoid unexpected synchronisation from the device.
The goal is to allow installation of stubs of libraries such as emlearn-micropython from PyPi once @jonnor has published it. |
|
"Problems" is fine
print(0x1.to_bytes(1))Using "Advanced Mode" and improving the suggestion for stubs selection is welcome! |
49baaf7 to
95402f2
Compare
|
@vshymanskyy and all others that may stumble on this. All things that I set out to do work, but there also some things that want to look into a bit further. (scope creep ?) For anyone wanting to try: Any feedback is appreceated. |
40dcd22 to
ccc9495
Compare
Add the pinned LSP client, Pyright worker, browser-test tooling, and matching runtime dependencies required by the type-checking integration. Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>
Add local package resolution, worker and stub asset staging, and focused tests for building ViperIDE against sibling type-checking packages. Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>
Add the browser type-checking service, runtime lifecycle, workspace mirror, verified stub selection, package installation and caching, and bundled Viper tools stubs with unit coverage. Fold shutdown, retry, race, and workspace consistency fixes into the initial service implementation. Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>
a7afff1 to
19dfd7f
Compare
Add reviewed type-checking defaults, stub controls, localized Problems presentation, accessibility-aware severity filtering and counts, responsive styles, and unit coverage. Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>
Add a shared input dialog and migrate standalone WebREPL and file prompt flows away from direct browser prompts. Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>
Wire type checking into application controllers, CodeMirror editors, cached and device files, board metadata, completions, mpy-cross diagnostics, package prompts, and runtime restarts. Preserve editor extensions and hide filtered diagnostics consistently across Problems and lint surfaces. Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>
Add deterministic Playwright fixtures and helpers, migrate browser workflows, block unintended network access, provide opt-in live package tests, and run the suite in PR CI. Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>
Install from lockfiles, preserve MicroPython-compatible minification, verify inlined assets, and version WebAssembly runtime URLs to avoid stale service-worker cache mismatches. Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>
Add the beta Pages workflow and isolate deployment concurrency so beta builds cannot cancel production releases. Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>
Document type-checking modes, runtime and stub selection, local package workflows, browser tests, and the provenance of bundled Viper tools stubs. Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>
20e8afe to
542a79c
Compare

Introduce a new type-checking service with
Adds dependencies and add a new Rollup loader.
Include tests for type-checking eligibility and expand localization for type-checking settings.
Currently I publish the components from github via immutable tags via the JSDeliver CDN
But intend to move to npm or similar - open to suggestions.
There is likely more fit and finish to do, I have tested against VMs and hardware, and have done my best to extend the test cases.
I have some documentation for the backend services that I want to push to RTD , for now it is in https://github.com/Josverl/stubs_playground/tree/integrate/docs
Closes: #4