make backslashes visible in docs for dict_add and dict_set#1372
Merged
oreflow merged 1 commit intobazelbuild:mainfrom Jun 20, 2025
Merged
make backslashes visible in docs for dict_add and dict_set#1372oreflow merged 1 commit intobazelbuild:mainfrom
oreflow merged 1 commit intobazelbuild:mainfrom
Conversation
In order to escape colons in the keys and values that you provide to dict_add and dict_set, you must precede them with backslashes. The raw README.md file has the backslashes, but they are not visibile when rendered. We here double these backslashes so that they'll be visible when rendered.
Contributor
Author
|
@oreflow FYI |
Collaborator
|
Nice, thanks for fixing this :) |
oreflow
approved these changes
Jun 20, 2025
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
2 participants
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.
In order to escape colons in the keys and values that you provide to dict_add and dict_set, you must precede them with backslashes. The raw README.md file has the backslashes, but they are not visible when rendered. We here double these backslashes so that they'll be visible when rendered.
This is a followup to #1361.