Track configuration token spans across mixed newline styles
Windows configuration files report errors one line late. Define offsets and line mapping for LF and CRLF.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Lexing · Source maps
Estimated field mix
- Compiler and language tooling100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional build tool Sprig reads a tiny configuration language with identifiers, strings, lists and assignments. Author the grammar and synthetic source corpus locally; parsing never executes source.
Setup prerequisites
- Write the tiny language grammar and generated source examples.
- Create fixtures with Unicode, truncated tokens and nested lists.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Spans cover exact token bytes or declared code units
- CRLF counts as one line break
- EOF has a valid location
Implementation constraints
- State the offset unit explicitly.
Verification to include
- Tokenize mixed newline fixture
- Locate error at EOF
Deliverables
- Span mapper and boundary cases
Rollout and recovery
Fall back to offsets if line mapping is unreliable.
Value of the work
For the engineer: Practice source positions, grammar boundaries and error recovery.
For the team: Inspect whether tooling errors help users correct configuration safely.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.