Update API Extractor line endings to 'lf' #6242
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Size Report 1Affected ProductsNo changes between base commit (936591c) and merge commit (6c88fd2).Test Logs |
Size Analysis Report 1Affected ProductsNo changes between base commit (936591c) and merge commit (6c88fd2).Test Logs |
hsubox76
approved these changes
May 9, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Update API Extractor config file to use POSIX-style newlines (lf) to remove inconsistencies on Github. We were having issues where git thought every new line in the md file was different instead of giving a useful diff report. As most users will be using lf line endings, we have changed the config to use this style. After all of the API documentation is regenerated, we should have useful diffs in github.