docs: update list marker detection references in parsing docs#74
Open
detail-app[bot] wants to merge 1 commit into
Open
Conversation
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.
Corrected stale documentation in all-parsing-and-markdown-logic.md that referenced non-existent methods. The 'List Marker Detection' section referenced 'fixInlineLists()' which never existed, and the 'List Processing Complexity' section incorrectly described client-side regex processing in markdown-utils.js which was removed in an earlier Svelte migration.
These inaccuracies would have led developers to search for non-existent code and misunderstand the current architecture where marker detection is consolidated in OrderedMarkerScanner.
Introduced by commit 60bdcab (@WilliamAGH)
Doc Drift PRs can be configured here.