non-greedy matching for Schema.String in Schema.TemplateLiteralParser#5322
Merged
gcanti merged 2 commits intoEffect-TS:mainfrom Aug 3, 2025
Merged
Conversation
Contributor
Author
|
@gcanti my mistake, I clearly missed some tests! Updating now... |
Contributor
|
@beezee no problem, great fix, I have already applied it in v4 |
🦋 Changeset detectedLatest commit: 2248b1e The changes in this PR will be included in the next version bump. This PR includes changesets to release 35 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
gcanti
approved these changes
Aug 3, 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
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.
Type
Description
This PR changes the regex used for Schema.String in TemplateLiteralParser from greedy to non-greedy (
[\\s\\S]*->[\\s\\S]*?). Greedy matching can consume too much input and prevent following spans from matching. The non-greedy version allows downstream segments to parse correctly.Minimal repro is shown in this playground: https://effect.website/play#a54077a17e06
Note the minimal repro avoids NumberFromString (case exercised in the added test) to avoid unsupported span error when extracting the regex via TemplateLiteral.
Related
This was discussed briefly here: https://discord.com/channels/795981131316985866/1344319931625246770