Consume published quarto-error-reporting 0.1.0 from crates.io (bd-egcyeym9, Phase 3 cutover)#350
Merged
Conversation
…(bd-egcyeym9) Phase 3 cutover: quarto-error-reporting has been extracted to https://github.com/posit-dev/quarto-error-reporting and published to crates.io as 0.1.0 (it depends only on the already-published quarto-source-map 0.1.0). Cut q2 over to the published crate: - [workspace.dependencies.quarto-error-reporting]: path -> version = "0.1.0" - 7 plain path-deps -> { workspace = true } - wasm-quarto-hub-client (excluded standalone workspace): direct quarto-error-reporting = { version = "0.1.0", features = ["json"] } - the json consumers (quarto, quarto-core, quarto-preview) keep features = ["json"] (now resolving to the external crate; json on workspace-wide via unification) - delete in-tree crates/quarto-error-reporting/ - quarto-error-catalog (the q2-side Q-* policy) now depends on the external crate. Cargo.lock resolves quarto-error-reporting 0.1.0 + transitively quarto-source-map 0.1.0 from the crates.io registry (matching checksums). CLAUDE.md crate layout updated: both foundation crates moved to an "Externalized foundation crates" section. Verified: cargo nextest run --workspace (10177 passed); full cargo xtask verify — all 14 steps incl. the WASM build + hub-client tests (precache under limit). 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.
Phase 3 cutover of the diagnostics-foundation extraction (strand bd-egcyeym9).
quarto-error-reportingnow lives at https://github.com/posit-dev/quarto-error-reporting and is published to crates.io as 0.1.0; q2 consumes it as a version dep. Both foundation crates (quarto-source-map,quarto-error-reporting) are now external.Builds on #348 (Phase 1) and #349 (Phase 2).
What this PR does
[workspace.dependencies.quarto-error-reporting]:path→version = "0.1.0"{ workspace = true }wasm-quarto-hub-client(excluded standalone workspace) → direct{ version = "0.1.0", features = ["json"] }quarto,quarto-core,quarto-preview) keepfeatures = ["json"], now resolving to the external cratecrates/quarto-error-reporting/quarto-error-catalog(the q2-sideQ-*policy) now depends on the external crateCLAUDE.mdcrate layout updatedCargo.lockresolvesquarto-error-reporting 0.1.0+ transitivelyquarto-source-map 0.1.0from the crates.io registry (matching checksums).Notes
schema_drifttest that q2's Linux+macOS CI never caught — fixed in the new repo with.gitattributes. (q2's in-tree copy had the same latent bug; deleting it here makes the point moot.)jsonfeature wiring from Make quarto-error-reporting catalog-agnostic; extract quarto-error-catalog (bd-egcyeym9, Phase 2) #349 carried over untouched.Verification
cargo nextest run --workspace— 10177 passedcargo xtask verify— all 14 steps green (incl. WASM build + hub-client tests; PWA precache under limit)Next
The YAML stack (
quarto-yaml+quarto-yaml-validation) — the original goal — perclaude-notes/plans/2026-06-26-extract-quarto-yaml-validation-design.md.🤖 Generated with Claude Code