getify/literalizer

Handle streaming lexing

Open

#20 opened on Sep 7, 2013

View on GitHub
 (4 comments) (0 reactions) (1 assignee)JavaScript (2 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (18 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

[edit: renamed to change the scope/intent of this bug per this comment: https://github.com/getify/literalizer/issues/20#issuecomment-23993775]

fs.readFile (and fs.readFileSync) provides a Buffer object. Passing this into literalizer.lex returns very unexpected data.

It would be great if it could read from the buffer directly, but if it requires string input, could you pass the input of "lex" through String()?

Contributor guide

Research direction
Investigate how literalizer.lex handles Buffer input. The fix could involve converting the Buffer to a string using String() or Buffer.toString() before processing, or modifying the lexer to accept Buffers directly.
Tech stack
javascript
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Node.jsBuffers
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60