Allow spaces in example references #388
Merged
Conversation
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
tyranron
added
enhancement
tyranron
approved these changes
Dec 23, 2025
src/feature.rs
Outdated
| #[expect(clippy::unwrap_used, reason = "regex is valid")] | ||
| static TEMPLATE_REGEX: LazyLock<Regex> = | ||
| LazyLock::new(|| Regex::new(r"<([^>\s]+)>").unwrap()); | ||
| LazyLock::new(|| Regex::new("<([^>]+)>").unwrap()); |
Member
There was a problem hiding this comment.
@aepfli allowing spaces seems ok, but does it mean we should also allow \t, \r, \n and other "brothers"?
I think it's only meaningful to allow spaces strictly. And only between non-space characters. Otherwise, this regex allows < > placeholder, which is weird.
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.
closes: #387