Ironclad / Ironclad/rivet

[Bug]: The string output of "Text" and "Read file" nodes converts all \n into \r\n

Open
#465 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
4.7k
Forks
388
PR merge metrics
No merged PRs in 30d

Description

### What happened?

When using "Text" and "Read file" nodes, the output string is different from what it was originally. Specifacally, all \n become \r\n

### What was the expected functionality?

All \n's stay \n's

### Describe your environment

Windows 10, Rivet IDE v1.9.0

### Relevant log output

_No response_

### Relevant screenshots

_No response_

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in the Rivet IDE on Windows 10 with the Text and Read file nodes, comparing their output with the original string. Trace the node output handling to find where LF newlines become CRLF, then verify that both nodes preserve \n in their output.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.