Skip to content

fix(yaml): keep patch state synchronized - #360

Open
dajiaohuang wants to merge 1 commit into
vercel-labs:mainfrom
dajiaohuang:fix-yaml-patch-state-359
Open

dajiaohuang wants to merge 1 commit into
vercel-labs:mainfrom
dajiaohuang:fix-yaml-patch-state-359

Conversation

@dajiaohuang

Copy link
Copy Markdown

Fixes #359. Apply RFC 6902 yaml-patch operations to the transform working spec before emitting each operation, so later yaml-edit fences use the renderer current state. Adds move/copy regressions and documents the behavior. Validation: pnpm --filter @json-render/yaml test (44 passed), pnpm --filter @json-render/yaml build, and pnpm --filter web exec fumadocs-mdx passed. Type-check caveat: repository-wide check is blocked by the existing Windows-incompatible rm -rf in @json-render/next; YAML package typecheck hits an unchanged TS2352 cast in transform.test.ts:45.

@vercel

vercel Bot commented Sep 25, 2026

Copy link
Copy Markdown
Contributor

@dajiaohuang is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Keep yaml-patch state in sync for later yaml-edit fences

1 participant