[p5.js 2.0+ Bug Report]: save() ignores the CRLF option when saving text files
Open
Beginner friendly
Nobody has claimed this yet.
Area:IO
p5.js 2.0+
- Dominant language
- JavaScript
- Stars
- 24k
- Forks
- 3.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 25
Description
Most appropriate sub-area of p5.js?
- Accessibility
- Color
- Core/Environment/Rendering
- Data
- DOM
- Events
- Image
- IO
- Math
- Typography
- Utilities
- WebGL
- WebGPU
- p5.strands
- Build process
- Unit testing
- Internationalization
- Friendly errors
- Other (specify if possible)
p5.js version
2.3.1
Web browser and version
Any
Operating system
No response
Steps to reproduce this
Steps:
- Create a new p5.js 2.0+ sketch.
- Add and run the following code.
- Inspect the downloaded output.txt file's line endings.
function setup() {
save(['a', 'b'], 'output', 'txt', true);
}
Can I be assigned this issue @ksen0
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 at the p5.js save() entry point and trace how the final true argument is handled when saving text. Run the provided sketch, inspect output.txt line endings, and confirm the completed behavior produces CRLF line endings when requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 74/100