Description
The current CI pipeline (.github/workflows/ci.yml) only checks oxide-browser and hello-oxide. Several other example crates are missing from CI:
examples/audio-player
examples/timer-demo
examples/index
examples/fullstack-notes/frontend (wasm32 target)
examples/fullstack-notes/backend (native target)
If any of these examples break due to SDK changes, we won't know until someone tries to build them manually.
What to do
- Add
cargo check --target wasm32-unknown-unknown for each WASM example crate to the check-sdk job
- Add
cargo check (native target) for the fullstack-notes/backend crate
- Optionally, add
cargo build for examples to ensure they produce valid .wasm output
Files involved
Difficulty
Beginner — just add a few lines to the existing CI workflow. Great way to learn GitHub Actions!
Description
The current CI pipeline (
.github/workflows/ci.yml) only checksoxide-browserandhello-oxide. Several other example crates are missing from CI:examples/audio-playerexamples/timer-demoexamples/indexexamples/fullstack-notes/frontend(wasm32 target)examples/fullstack-notes/backend(native target)If any of these examples break due to SDK changes, we won't know until someone tries to build them manually.
What to do
cargo check --target wasm32-unknown-unknownfor each WASM example crate to thecheck-sdkjobcargo check(native target) for thefullstack-notes/backendcratecargo buildfor examples to ensure they produce valid.wasmoutputFiles involved
.github/workflows/ci.ymlDifficulty
Beginner — just add a few lines to the existing CI workflow. Great way to learn GitHub Actions!