fix: customised recipe to yaml string to avoid minininjia parsing error

[lifeizhou-ap]

Summary

This fix is for a recipe with backtick and {{if}} block

Issue

serde_yaml serialization uses internal heuristics to decide between | and quoted text with escaped\n and \", and the quoted form breaks MiniJinja parsing. It seems that if the texts contains backtick, it tends to use the quoted texts without "|"

Example before:

prompt: "Hello \\\"World\\\"\\n{% if user == \\\"admin\\\" %}Welcome{% endif %}"

After fix:

prompt: |
   Hello "World"
  {% if user == "admin" %}Welcome{% endif %}

Changes

Apply extra format after the yaml serialization to convert the quoted multiline texts to the texts with "|"

Type of Change

• Feature
• Bug fix
• Refactor / Code quality
• Performance improvement
• Documentation
• Tests
• Security fix
• Build / Release
• Other (specify below)

Testing

Unit testing and manual testing

[lifeizhou-ap]

.bundle

[lifeizhou-ap]

.bundle

[Copilot]

Pull Request Overview

This PR introduces a utility module to normalize multi-line YAML string formatting to fix issues with MiniJinja template parsing. The changes address a problem where serde_yaml sometimes uses quoted strings with escaped newlines and quotes, which breaks MiniJinja parsing.

Key changes:

• Added new yaml_format_utils.rs module with a function to reformat multi-line string fields in YAML
• Added to_yaml() method to the Recipe struct that applies this reformatting
• Updated recipe serialization calls in recipe_utils.rs to use the new to_yaml() method

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
crates/goose/src/recipe/yaml_format_utils.rs	New utility module that transforms quoted multi-line strings to YAML literal block format and handles unescaping
crates/goose/src/recipe/mod.rs	Added to_yaml() method to Recipe struct and module declaration for yaml_format_utils
crates/goose-server/src/routes/recipe_utils.rs	Updated two functions to use Recipe's new to_yaml() method instead of direct serde_yaml::to_string()

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The detection logic checks for literal \\n in the string, but this may not correctly identify all multi-line strings. Consider checking for both \\n (single backslash) and \\\\n (double backslash) patterns, or using a more robust method to detect escaped newlines in serialized YAML strings.

Suggested change

	if raw_val.contains("\\n") {
	if raw_val.contains("\\n") || raw_val.contains("\\\\n") {

[Copilot]

[nitpick] The list of fields to reformat is hardcoded here. Consider making this configurable or deriving it from the Recipe struct to ensure all relevant string fields are handled consistently as the struct evolves.

Suggested change

	reformat_fields_with_multiline_values(&recipe_yaml, &["prompt", "instructions"]);
	Ok(formatted_recipe_yaml)
	}
	reformat_fields_with_multiline_values(&recipe_yaml, Self::multiline_fields());
	Ok(formatted_recipe_yaml)
	}
	/// Returns the list of Recipe fields that should be reformatted for multiline YAML output.
	fn multiline_fields() -> &'static [&'static str] {
	&["prompt", "instructions"]
	}