Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Carriage return handling #16

Merged
merged 8 commits into from
Sep 9, 2023
Merged

Carriage return handling #16

merged 8 commits into from
Sep 9, 2023

Conversation

nedtwigg
Copy link
Member

We don't preserve carriage returns in general, e.g.

but we do want to keep whatever the user has. We use exclusively \n internally, but if a user is using \r\n we should not bother them with this triviality.

@jknack this is a nice easy warmup, no dependencies on any of the other open PRs.

@jknack
Copy link
Collaborator

jknack commented Sep 9, 2023

@nedtwigg just pushed a new line reader

- redo jvm line reader to keep incremental reads and figure it out useUnixNewLines
- still got some failures, but want to get feedback about the line reader
Copy link
Member Author

@nedtwigg nedtwigg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The carriage return stuff looks great, not sure why the other tests are failing.

- there was setting the content to just `\r\n` or `\n` produces an empty snapshot making the build unstable
- it must assume always unixline
@jknack jknack merged commit c8e150e into main Sep 9, 2023
6 checks passed
@nedtwigg nedtwigg deleted the feat/carriage-return branch September 10, 2023 04:20
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