Fix visible \n characters in README's mermaid diagram #72
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.
The mermaid diagram in the README contained visible
\ncharacters instead of proper line breaks, making the flowchart difficult to read. These literal\ncharacters appeared in three node labels within the decision tree diagram:id2B: "Do you want to add an unsupported package? \n either a package..."id2C: "Do you want to use Mariner for your project? \n ex. bare metal..."id3B: "Do you want to add a common package? \n either a package..."Changes made:
\ncharacters with proper<br>tags in the mermaid flowchartResult:
The mermaid diagram now renders with proper multi-line text formatting instead of showing raw
\ncharacters, improving readability of the decision tree that helps users choose between the CBL-Mariner and CBL-MarinerTutorials repositories.Fixes #71.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.