docs: clarify system separator fields - #2371
Open
Himanshuagrawal4 wants to merge 1 commit into
Open
Conversation
Himanshuagrawal4
marked this pull request as ready for review
August 10, 2026 09:00
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
Clarify that Hatch's system separator context fields must be written as
{/}and{;}, that literal separator characters are unchanged, and show their platform-specific expansions.Fixes #2026.
Validation
Contexttests for directory and path separators: 2 passedgit diff --checkThe strict social-card build remains unavailable in this Windows environment because of the existing native Cairo dependency.
AI assistance
Codex (GPT-5) assisted with drafting the documentation. I manually reviewed the final diff and verified the examples against Hatch's existing context formatter tests.