Skip to content

Fix heading recognition in readme processing - #5

Merged
aks129 merged 1 commit into
FHIR-IQ:mainfrom
tschwirt:windows-readme-fix
Aug 16, 2026
Merged

Fix heading recognition in readme processing#5
aks129 merged 1 commit into
FHIR-IQ:mainfrom
tschwirt:windows-readme-fix

Conversation

@tschwirt

Copy link
Copy Markdown
Contributor

Enhanced processing to support CRLF line endings (e.g., on Windows). Update tests to validate handling of Setext headings and CRLF line endings in readme sections.

Enhanced processing to support CRLF line endings (e.g., on Windows). Update tests to validate handling of Setext headings and CRLF line endings in readme sections.
@vercel

vercel Bot commented Aug 14, 2026

Copy link
Copy Markdown

@tschwirt is attempting to deploy a commit to the aks129's projects Team on Vercel.

A member of the Team first needs to authorize it.

aks129 added a commit that referenced this pull request Aug 15, 2026
Tim reported the CRLF bug and said he had fixed it locally and would open a
separate pull request. He did, as #5. I fixed it myself and pushed before
looking at his branch, which would have meant closing a first contributor's
first pull request as already done. That is a bad trade at any time and a
worse one here, where the repository still shows a single author.

His fix is correct and comes with tests. It makes the heading patterns tolerate
a trailing CR rather than changing how the file is split. I would have done it
at the split, and that preference is not worth overriding someone who found the
bug, diagnosed it, and wrote the tests.

This restores readme.ts and drops the duplicate tests so #5 applies cleanly.
The terminology fixes in the same commit stay: they are unrelated and his branch
does not touch them.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Package validation

No package changed in this pull request, so there was nothing to validate.

@aks129
aks129 merged commit b72623a into FHIR-IQ:main Aug 16, 2026
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants