This repository was archived by the owner on Feb 17, 2026. It is now read-only.
Fix Ex 5 in the tutorial to match its expansion#564
Open
felipethome wants to merge 1 commit intosweet-js:masterfrom
Open
Fix Ex 5 in the tutorial to match its expansion#564felipethome wants to merge 1 commit intosweet-js:masterfrom
felipethome wants to merge 1 commit intosweet-js:masterfrom
Conversation
Member
|
Right, you would need to check to make sure the |
Author
|
But don't you think it is nice for the user to see |
Member
|
Actually, why don't you remove the |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The expansion of the example 5 in the tutorial, with sweet.js version 2.0.0, gives for me:
So I added one more ctx.next() and rebuild the docs. Maybe would be better also a check to see if the
;exists?