Update Lexer section in USING_PRO.md #3317
Merged
Conversation
This file contains 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
- Clarified that `marked.lexer()` does not retain tokens from previous calls. - Clarified that `new marked.Lexer().lex()` accumulates tokens from successive calls. Closes markedjs#3316.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Marked version: all
Markdown flavor: n/a
Description
marked.lexerornew marked.Lexer#3316.Expectation
Documentation should be explicit for new users when using Lexer.
Result
User is now informed of different behaviors when using
marked.lexerornew marked.Lexer.What was attempted
n/a
Contributor
Committer
In most cases, this should be a different person than the contributor.