Fix parseStrict README example - #294
Open
alan747271363-art wants to merge 1 commit into
Open
Conversation
lbesecker195
approved these changes
Sep 13, 2026
lbesecker195
left a comment
lbesecker195
left a comment
There was a problem hiding this comment.
str is not defined in the example; s is the parameter. The // tsc error comment still applies since a plain string is not a StringValue. LGTM.
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.
Summary
Fixes the
parseStrictREADME example so it passes the function argumentsinstead of the undefinedstridentifier.Validation
git diff --checkThis is a docs-only change. I also attempted the full test script locally, but this checkout has no installed
node_modules, so the package test script could not start.