Currently the replacing of line endings is wrong and too late. Rather than replacing "\r\n" which represents a windows line ending only "\r" is replaced resulting in double line endings on files with CRLF-endings.
Unfortunalty just adjusting the replacement from "\r" to "\r\n" breaks the formatting as the parser above also depends on UNIX-lineendings.
TODO:
[ ] unmarshalling does not work on windows (the common config does not auto resolve) @daixiang0 would be cool, if you could provide some input on how the unmarshaling works
Fix line endings for windows.
Currently the replacing of line endings is wrong and too late. Rather than replacing "\r\n" which represents a windows line ending only "\r" is replaced resulting in double line endings on files with CRLF-endings.
Unfortunalty just adjusting the replacement from "\r" to "\r\n" breaks the formatting as the parser above also depends on UNIX-lineendings.
TODO: