Problem/Motivation
I have file types I need to serve where the type of line endings matters (.pem, for example). I’d love to be able to use this module for those. Right now, I believe you end up with CRLF when you use a Windows browser to edit the file contents, and probably LF if you use Mac or Linux (I haven’t verified this).
Steps to reproduce
1. Create a plain text file config entity using a Windows browser.
2. Download the file.
3. Observe that its line endings are CRLF (cat -e filename.txt).
Proposed resolution
My honest opinion is that CRLF line endings are essentially never what you want in this situation, so I could see solving this by just forcing LF line endings, but probably a dropdown allowing the user to choose would be more polite. Such a dropdown would need to have its default value, for existing files, come from the existing line endings.
Remaining tasks
determine if this feature is acceptable for a module in maintenance mode only; agree on approach; implement
User interface changes
Potentially a dropdown allowing a choice of line endings.
API changes
None.
Data model changes
None.
Comments