fix(setup): block-style YAML for Goose and Hermes configs - #29
Merged
Merged
Conversation
An empty config file (and --print) started from parseDocument("{}"), so
the root was a flow mapping and the whole file rendered as one {...}
blob. Start from a fresh Document instead; existing files keep their
style as before.
Co-Authored-By: Claude Fable 5.1 <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.
Summary
summer setup gooseon an empty config (and--printfor goose/hermes) rendered the file as one flow mapping ({ extensions: { ... } }) because the writer started fromparseDocument("{}"). It now starts from a freshDocument, so new files are block-style YAML like every hand-written Goose config. Existing files are untouched in style, as before.Test plan
npx vitest run1483 pass🤖 Generated with Claude Code