feat: add parseMany() for multi-content markdown - #24
Open
ek9r wants to merge 2 commits into
Open
Conversation
Splits content into multiple independently-parsed parts via < next --> / < next: name --> markers. Non-breaking: ParsedMarkdown gets an optional $name, and parseMany() returns a ParsedMarkdownCollection (mirrors the existing TokenCollection).
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
1 participant
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 #17
Adds parseMany(), splitting one piece of content into multiple independently-parsed parts
via
<!-- next -->/<!-- next: name -->markers. Doesn't change any existing behavior.Cleaned up relative to the POC-branch linked in #17: dropped the dev-only bin/ scripts and demo content used for evaluation, kept only the feature itself, its tests, and the README addition.
Thanks for the quick feedback @brendt and the go-ahead, to @defautset for kicking the tires on the branch early with a tiny presentation demo (never seen a Composer install bootstrapped straight inside a single PHP script like that, wonderfully crazy), and to @kchaot for spotting the unblog.