- #Visual studio community for mac convert line endings pdf#
- #Visual studio community for mac convert line endings code#
Let us create a Monaco instance with a string of every single extended ASCII character: let chars = įor (let i = 0 i you look very carefully, you can spot the difference. Let’s check how close Monaco gets to getValue(setValue(s)) = s. But that still leaves the body, which can have a mix of everything that needs to be preserved at all costs. If we’re just talking about the headers, I could use getValue() to force normalized line-breaks. But the body on the other hand might follow completely arbitrary other rules, not related to HTTP. Obviously I absolutely need to preserve CRLF for the header block. My current use-case that I’m evaluating Monaco for is editing raw HTTP requests/responses. I would expect getValue(setValue(s)) = s for every string s. Strings don’t have a concept of line endings. Since Monaco was extracted from VS Code, we are not longer talking about “files”. And all line ending related issues in Monaco point to this, so here I am. I’m not using VS Code, but I’m evaluating Monaco. I for one would love to hear some member giving this another look. But it’s a persistent open issue and therefore should at least be reevaluated, imho. I don’t know if about 10 different examples collected over 5 years is enough to persuade somebody to work on this. If for some reason I have to edit a testfile with mixed line endings I will lose what a test case is supposed to test. My own example: files for tests (since some external systems work with differnet line endings) cannot be edited in VS Code.
#Visual studio community for mac convert line endings pdf#
Working on PDF files with mixed lines endings becomes impossible.unable to editing raw HTTP requests and responses through the Monaco Editor.XML documents with CDATA entries with different line endings cannot be edited savely.SQL exports which contain LF as line endings but also CRLF within multi-line text fields.
#Visual studio community for mac convert line endings code#
gitignore files with Icon\r\r lines in VS Code will break these files behavior (in any case everyone has to be aware of the issue to make the workaround of using Icon? work) Cross platform dev teams might suffer from normalization ping pong.Makes editing files with binary payloads impossible (shell scripts with binary blob).You might think that mixed line endings are a bad idea, but are not in a position to change current policy.PRs/Changes to repos with mixed line endings become impossible to do (because much bigger diffs are generated by the normalization).
Concrete examples where this is a problem (from this thread):
0 kommentar(er)
