Structured Headers don't support CRLF line terminators
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 245
- Forks
- 80
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 2
Description
If the spec text contains CRLF in a structured header, ecmarkup reports an expected parameter name warning for any parameters. Changing all CRLF characters to LF makes the warning go away, however not supporting CRLF is problematic for Windows users.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the warning with a structured header containing CRLF line terminators, then trace the structured-header parsing entry point. Done means CRLF input no longer produces the expected parameter name warning while LF input continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100