Repository navigation
Restore UTF-8 BOM on RuleCompiler.cs - #764
Merged
Merged
Conversation
microsoft#759 re-saved RuleCompiler.cs without its UTF-8 BOM. Restore it so the file matches its original encoding; no other change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
YogeshPraj
approved these changes
Nov 4, 2026
YogeshPraj
enabled auto-merge (squash)
November 4, 2026 17:08
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
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.
My #759 re-saved
src/RulesEngine/RuleCompiler.cswithout its UTF-8 BOM. It's the same encoding problem you flagged on #755–#758, and it slipped through on this one before it was merged. This restores the BOM. The file is otherwise byte-for-byte identical tomain(LF line endings unchanged), so the diff is only line 1.I've also added an encoding check on my side before pushing, so this shouldn't happen again.
🤖 Generated with Claude Code