Preserve ordered-list starting numbers in Markdown - #149
Merged
Merged
Conversation
ralyodio
added a commit
that referenced
this pull request
Sep 21, 2026
Each of these PRs passed alone and failed together: - #149 emits start="N" on ordered lists, so the #161 marker-width tests that begin at 12345 now expect the attribute. - #131 resolves every federated host before connecting, so the #128 directory salary tests pass allowPrivate like the other federation tests do. Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
ralyodio
added a commit
that referenced
this pull request
Sep 21, 2026
* Use parser decisions to deduplicate resume export headers * test: reconcile expectations after the 2026-09-21 batch merge Each of these PRs passed alone and failed together: - #149 emits start="N" on ordered lists, so the #161 marker-width tests that begin at 12345 now expect the attribute. - #131 resolves every federated host before connecting, so the #128 directory salary tests pass allowPrivate like the other federation tests do. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Anthony Ettinger <anthony@profullstack.com> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
ralyodio
added a commit
that referenced
this pull request
Sep 21, 2026
* Continue job import after incomplete structured postings * test: reconcile expectations after the 2026-09-21 batch merge Each of these PRs passed alone and failed together: - #149 emits start="N" on ordered lists, so the #161 marker-width tests that begin at 12345 now expect the attribute. - #131 resolves every federated host before connecting, so the #128 directory salary tests pass allowPrivate like the other federation tests do. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Anthony Ettinger <anthony@profullstack.com> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
ralyodio
added a commit
that referenced
this pull request
Sep 21, 2026
* Preserve parentheses in Markdown link destinations * test: reconcile expectations after the 2026-09-21 batch merge Each of these PRs passed alone and failed together: - #149 emits start="N" on ordered lists, so the #161 marker-width tests that begin at 12345 now expect the attribute. - #131 resolves every federated host before connecting, so the #128 directory salary tests pass allowPrivate like the other federation tests do. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Anthony Ettinger <anthony@profullstack.com> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
ralyodio
added a commit
that referenced
this pull request
Sep 21, 2026
* Preserve parentheses in Markdown link destinations * Keep Markdown tables from swallowing following blocks * test: reconcile expectations after the 2026-09-21 batch merge Each of these PRs passed alone and failed together: - #149 emits start="N" on ordered lists, so the #161 marker-width tests that begin at 12345 now expect the attribute. - #131 resolves every federated host before connecting, so the #128 directory salary tests pass allowPrivate like the other federation tests do. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Anthony Ettinger <anthony@profullstack.com> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
ralyodio
added a commit
that referenced
this pull request
Sep 21, 2026
* Skip empty Word text elements without consuming following content * test: reconcile expectations after the 2026-09-21 batch merge Each of these PRs passed alone and failed together: - #149 emits start="N" on ordered lists, so the #161 marker-width tests that begin at 12345 now expect the attribute. - #131 resolves every federated host before connecting, so the #128 directory salary tests pass allowPrivate like the other federation tests do. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Anthony Ettinger <anthony@profullstack.com> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
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.
Markdown ordered lists lose their starting number:
3. Reviewfollowed by4. Deliverdisplays as steps 1 and 2, and a step-zero prerequisite also displays as step 1.Preserve the first ordered marker as the HTML
startattribute when it differs from 1. Lists starting at 1 retain their existing output. The focused regressions cover starts 0 and 3,)markers, leading-zero normalization and nested starts; unordered lists and list separation remain unchanged.Validation: baseline assertions fail against upstream
282feb1and pass with the fix. All four ordinary list tests pass usingnode --test --test-name-pattern='ordered|lists keep' test/markup.test.ts. Production build, test TypeScript checking andgit diff --checkpass. Tests use offline text fixtures; no live-service or unrelated security tests were run.Submitted under the published $0.25 USD-equivalent reward per valid bug-fix PR, using the existing application and settlement conversation. Requested settlement remains native SOL on Solana mainnet, with acceptance and the exact net token amount confirmed before payment.