re-exports: fix generated eol #10779
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Depending on the Git configuration of the cloned projects, the EOL might
differ from the OS recommended one. On Windows Git might use \n in place
of \r\n for example.
Implement a small scan to figure out what is the current EOL before
generating the re-export files.
Here's an example of what I see with
git statusafter runningyarnon Windows:And Git being the nice guy he his, outputs the following when doing
git add .:In the end this means Git won't count those diffs for real, but it's annoying.
How to test
Running
yarnon Windows should not dirty your Git index anymore.Review checklist
Reminder for reviewers