Extract quarto-source-map to its own crates.io crate; q2 consumes 0.1.0 (bd-egcyeym9)#348
Merged
Merged
Conversation
…tion plans (bd-egcyeym9)
Design artifacts for pulling the diagnostics-foundation crates out of the q2
monorepo into standalone posit-dev/ repos:
- claude-notes/designs/cross-package-error-codes.md — the general two-identity
error-code discipline: package-owned origin codes vs product-owned
presentation codes, the remap that bridges them, the tier1/tier2/forbidden
fallback hierarchy, per-node definer/remapper roles, terminal-vs-remapped
inert provenance, and append-only ("cool URLs") code lifecycle.
- claude-notes/plans/2026-06-26-extract-error-reporting-foundation.md — phased,
leaf-first plan to extract quarto-source-map then quarto-error-reporting.
- claude-notes/plans/2026-06-26-extract-quarto-yaml-validation-design.md — the
YAML-stack extraction design (gated behind the foundation).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…gcyeym9) quarto-source-map has been extracted to https://github.com/posit-dev/quarto-source-map and published to crates.io as 0.1.0 — the first of the diagnostics-foundation crates to leave the monorepo. Cut q2 over to the published crate: - [workspace.dependencies.quarto-source-map]: path -> version = "0.1.0" - 13 main-workspace members: path dep -> { workspace = true } - wasm-quarto-hub-client (excluded, standalone workspace, refs every q2 crate by path): direct quarto-source-map = "0.1.0" — it cannot inherit a workspace dep, so { workspace = true } would fail to resolve at the wasm32 build. - delete in-tree crates/quarto-source-map/ - both Cargo.lock files now resolve quarto-source-map from the crates.io registry (matching checksum). wasm-quarto-hub-client/Cargo.lock additionally picks up incidental 0.5.0 -> 0.7.0 member-version catch-up that was already pending (pre-existing lockfile drift, regenerated by the build). Verified: cargo build --workspace; cargo nextest run --workspace (10238 passed); full cargo xtask verify — all 14 steps incl. the WASM build and hub-client tests. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First step of extracting the diagnostics-foundation crates out of the q2 monorepo
into standalone
posit-dev/repos (strand bd-egcyeym9). Leaf-first: this isthe trivial leaf, done first to exercise the whole repo → crates.io → q2-cutover →
WASM pipeline before the harder
quarto-error-reportingcarve-up.What this PR does
quarto-source-mapnow lives at https://github.com/posit-dev/quarto-source-mapand is published to crates.io as 0.1.0. q2 consumes the published crate:
[workspace.dependencies.quarto-source-map]:path→version = "0.1.0"{ workspace = true }wasm-quarto-hub-client(excluded standalone workspace): a directquarto-source-map = "0.1.0"— it can't inherit a workspace dep, so{ workspace = true }fails at the wasm32 build. (This was the one footgun;the WASM build caught it.)
crates/quarto-source-map/deletedCargo.locks resolve the crate from the crates.io registry with matchingchecksum.
wasm-quarto-hub-client/Cargo.lockalso absorbs incidental0.5.0 → 0.7.0member-version catch-up (pre-existing lockfile drift).Plus the design artifacts for the larger extraction (
claude-notes/designs/cross-package-error-codes.mdand the two extraction plans).Verification
cargo build --workspace✅cargo nextest run --workspace— 10238 passed ✅cargo xtask verify— all 14 steps incl. the WASM build and hub-client tests ✅Follow-ups (not in this PR)
posit-dev/quarto-source-maprepo (validated locally only).cargo owner --add github:posit-dev:<team> quarto-source-map(deferred).quarto-error-reporting(after splitting out theQ-*catalog data).🤖 Generated with Claude Code