feat: Support headerless table syntax - #8
Merged
Merged
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.
Summary
<thead>for headerless tables while retaining<tbody>rows.Example
renders as a table containing only
<tbody>, with the first column aligned left and the second aligned right.Validation
git diff --checkPerformance and memory
Benchmarks used five runs per scenario with the same Node/Vitest setup and 500-row inputs. Values below are medians per parse/render iteration.
+4.2%)+12.0%)+12.1%)-40.6%)+5.7%)-74.9%)The headerless case has no semantically equivalent baseline because the previous implementation treated the separator-first input as ordinary text. Its absolute cost is lower than the existing 500-row headed-table path. The aligned headed output now includes the required alignment attributes, so its time comparison includes the additional HTML output work.
Package size
The package has no build script and exports source files directly.
npm packcomparison againstorigin/mainshowed:33,996→35,200bytes (+1,204,+3.54%).203,166→207,479bytes (+4,313,+2.12%).The size increase includes the implementation, renderer changes, and regression tests.