slint-mapping 0.1.0

## slint-mapping recipes
##
## Run `just` (no args) to list everything. Most recipes wrap one or
## two `cargo` invocations; the value-add over typing cargo directly
## is documentation + sensible default flags + the `publish-check`
## aggregator.

_default:
    @just --list --unsorted

## ─── Development loop ──────────────────────────────────────────────

# Format every Rust source in-place.
fmt:
    cargo fmt --all

# Refuse to modify; useful in CI.
fmt-check:
    cargo fmt --all -- --check

# Lint everything, denying warnings.
clippy:
    cargo clippy --all-targets --all-features -- -D warnings

# Type-check the whole workspace (compiles every .slint via build.rs).
check:
    cargo check --all-targets --all-features

# Run unit + integration tests.
test:
    cargo test --all-features

# What CI runs on every PR.
ci: fmt-check clippy check test

## ─── Pre-publish hygiene tools ─────────────────────────────────────

# Install every tool the publish-check recipes depend on (idempotent).
install-publish-tools:
    cargo install --locked cargo-semver-checks
    cargo install --locked cargo-audit
    cargo install --locked cargo-deny
    cargo install --locked cargo-machete
    cargo install --locked cargo-msrv
    cargo install --locked cargo-public-api
    cargo install --locked cargo-release
    cargo install --locked typos-cli
    cargo install --locked trunk

# Detect breaking API changes since the last released version.
# Skips cleanly on the very first publish (no baseline on crates.io
# yet) — cargo-semver-checks errors with "<crate> not found in
# registry" which we detect here and turn into a no-op. After the
# first release the recipe runs normally.
semver-check:
    #!/usr/bin/env bash
    set -eo pipefail
    log=$(mktemp)
    # `pipefail` makes the `if` see the cargo exit code (not tee's
    # always-zero), so a real failure routes to the elif/else branch.
    if cargo semver-checks check-release 2>&1 | tee "$log"; then
        rm -f "$log"
    elif grep -q "not found in registry" "$log"; then
        rm -f "$log"
        echo
        echo "semver-check skipped: slint-mapping has no published baseline yet"
    else
        rm -f "$log"
        exit 1
    fi

# Scan deps for known CVEs (RustSec advisory database).
audit:
    cargo audit

# Enforce license / advisory / source policy (config: deny.toml).
deny:
    cargo deny check

# Find dependencies listed in Cargo.toml but never used.
machete:
    cargo machete

# Bisect the minimum Rust toolchain that still compiles the crate.
msrv:
    cargo msrv find

# Diff the public API against the last published version.
public-api:
    cargo public-api --diff-git-checkouts

# Build docs the way docs.rs builds them (--no-deps --all-features).
doc:
    RUSTDOCFLAGS="-D warnings" cargo doc --no-deps --all-features

# Look for typos in source, comments, and docs.
typos:
    typos

# Run every pre-publish check (~minutes); fast-fail tools run first.
publish-check: fmt-check typos clippy check test doc machete audit deny semver-check
    @echo "──────────────────────────────────────────"
    @echo "  publish-check ✓ — slint-mapping is shippable"
    @echo "──────────────────────────────────────────"

## ─── Release flow ──────────────────────────────────────────────────

# Dry-run the publish step without uploading.
publish-dry:
    cargo publish --dry-run

# Bump version + tag + push + publish via cargo-release (run publish-check first).
# Examples: `just release patch` (0.1.0 → 0.1.1), `just release minor`, `just release 0.3.0`.
# CARGO_HTTP_DEBUG=true surfaces the actual HTTP response body when
# crates.io rejects the upload — without it, cargo cuts off useful
# errors like "verified email required" or "name reserved" and you
# get a near-empty `body:` line in the output instead.
release LEVEL="patch":
    CARGO_HTTP_DEBUG=true cargo release {{LEVEL}} --execute

## ─── Local wasm preview ────────────────────────────────────────────
##
## `trunk` builds the wasm-demo, serves it on a local port, and
## auto-reloads the browser on source changes — single tool, no
## Python / Node / wasm-pack juggling. Install once with
## `cargo install trunk` (or via `just install-publish-tools`,
## which now bundles it in).

# Dev loop: build + serve + hot-reload on http://127.0.0.1:8765/.
# Edit any .rs / .slint / .html and the page rebuilds + reloads.
serve:
    cd wasm-demo && trunk serve

# Build the wasm-demo for release into wasm-demo/dist/. Used by the
# Pages workflow; the `--public-url` flag is what makes the asset
# URLs work when deployed under `/slint-mapping/` on github.io.
build-wasm:
    cd wasm-demo && trunk build --release --public-url /slint-mapping/