Migrate FigCraft to egui 0.37 (#1312)

* E21: require release font coverage and stabilize capture deadline tests

* E21: separate capture, IME and field-save regression phases

* M0: correct the migration qualification reference

* M-egui037: document input lifecycle and UI regression contracts

* M0: correct egui 0.37 status docs and stabilize join-code regression

---------

Co-authored-by: Dylan M. Taylor <dylan@dylanmtaylor.com>
Co-authored-by: Codebuff <noreply@codebuff.com>
This commit is contained in:
skylar taylor-barrick
2026-10-25 15:04:39 -04:00
committed by GitHub
co-authored by Dylan M. Taylor Codebuff
parent 3fc005c7fe
commit 236f3185d6
134 changed files with 7698 additions and 1396 deletions
+4 -1
View File
@@ -390,7 +390,10 @@ image sizes) and refuses it if anything is off.
`cargo xtask plugins` (part of `cargo xtask wasm` and `cargo xtask ci`; it needs the
`wasm32-unknown-unknown` target: `rustup target add wasm32-unknown-unknown`) checks, tests and
builds them, and leaves each example's manifest and module side by side in
`target/plugins/dist/<example>/`, ready to import.
`target/plugins/dist/<example>/`, ready to import. With `CARGO_TARGET_DIR` set, that location is
`$CARGO_TARGET_DIR/plugins/dist/<example>/`. Plugin compilation and host tests use the caller's
same Cargo target directory; wasm modules are built under its `wasm32-unknown-unknown/release/`
directory. The plugin workspace keeps its own lockfile and release profile.
A plugin of your own: