Fix table parsing and auto-format reliability#13
Draft
krotname wants to merge 1 commit into
Draft
Conversation
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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.
What changed
Why
Several independent edge cases could corrupt converted text, misidentify prose as a table, split a grapheme cluster, trigger stale automatic formatting after a manual edit, or perform quadratic work on large documents/cells.
Impact
Table editing and conversion are safer and more predictable. Automatic formatting now coalesces rapid edits, stays scoped to active Markdown editors, and remains cancelable. The shared Java/C++ golden fixture documents the cross-plugin behavior.
Validation
gradlew.bat check buildPlugin corePerformance --offline --no-daemon --console=plain --no-build-cache --rerun-tasksgit diff --checkpassed