respect end_of_line and charset in editorconfig#973
Merged
Conversation
cfbao
changed the title
j3parker
approved these changes
Apr 16, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Depending on the OS, the source generator uses different EOL for these two lines (added using
StringBuilder.AppendLine):When the generated code is committed and kept in sync with CI (e.g. in opensearch-infrastructure), this can cause frequent drifts because dev machines and actions runners use different OSes.
This PR uses
end_of_linefrom editorconfig as the source of truth to resolve this issue.Also added support for charset. Not having this doesn't cause drift, but it's just nice to have, and it's supported in a similar way.
VUL-1128