Playbook editor: support triple-backtick fenced code - #1281
Merged
Conversation
…code-editing # Conflicts: # specs/0050-playbook-builtin-template-content.md
…code-editing # Conflicts: # crates/cli/src/ui.rs
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
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.
Summary
specs/0204-playbook-code-editing.mdand evolve it to cover both single- and triple-backtick behaviorLatest-main integration
origin/mainata419c1cvia merge commit9f126acVerification
cargo buildcargo test -p construct-cli --bin construct playbook(352 passed; includes single/triple delimiters, Backspace/retype, CJK, painted-buffer differential geometry, and selection-menu tests)cargo test -p construct-e2e --test playbook_view(8 passed)cargo test -p construct-e2e --test web_smoke(2 passed)rustfmt --edition 2021 --check crates/cli/src/playbook_markdown.rsgit diff --checkMultiline constraint
The Playbook editor keeps a stable one-source-line/one-edit-row and collaboration-offset model. Therefore multiline fences remain visible literal source instead of collapsing opener/closer rows differently across clients. The completed one-line triple form provides delimiter-hidden editing parity without violating those invariants.