Repository navigation
Strip a leading BOM from string input - #606
Merged
Merged
Conversation
GrahamCampbell
force-pushed
the
fix/bom-string-input
branch
from
August 24, 2026 01:01
a6b0d6f to
8ea8e00
Compare
GrahamCampbell
force-pushed
the
perf/resolver-fewer-copies
branch
2 times, most recently
from
August 24, 2026 10:44
4bff462 to
c535a66
Compare
GrahamCampbell
force-pushed
the
fix/bom-string-input
branch
from
August 24, 2026 10:44
8ea8e00 to
515e483
Compare
GrahamCampbell
force-pushed
the
perf/resolver-fewer-copies
branch
from
August 24, 2026 13:24
c535a66 to
aa1dc16
Compare
GrahamCampbell
force-pushed
the
fix/bom-string-input
branch
from
August 24, 2026 13:24
515e483 to
48062f6
Compare
GrahamCampbell
force-pushed
the
perf/resolver-fewer-copies
branch
from
August 24, 2026 17:28
aa1dc16 to
3e31e8a
Compare
GrahamCampbell
force-pushed
the
fix/bom-string-input
branch
from
August 24, 2026 17:28
48062f6 to
fd5c7d4
Compare
GrahamCampbell
force-pushed
the
perf/resolver-fewer-copies
branch
from
August 24, 2026 17:43
3e31e8a to
e3f463e
Compare
GrahamCampbell
force-pushed
the
fix/bom-string-input
branch
from
August 24, 2026 17:43
fd5c7d4 to
3054315
Compare
GrahamCampbell
force-pushed
the
perf/resolver-fewer-copies
branch
from
August 24, 2026 17:46
e3f463e to
7d5abcc
Compare
GrahamCampbell
force-pushed
the
fix/bom-string-input
branch
from
August 24, 2026 17:46
3054315 to
4772134
Compare
GrahamCampbell
force-pushed
the
perf/resolver-fewer-copies
branch
from
August 24, 2026 17:47
7d5abcc to
1b25377
Compare
GrahamCampbell
force-pushed
the
fix/bom-string-input
branch
from
August 24, 2026 17:47
4772134 to
95f756f
Compare
GrahamCampbell
force-pushed
the
perf/resolver-fewer-copies
branch
from
August 24, 2026 17:49
1b25377 to
c0cbba6
Compare
GrahamCampbell
force-pushed
the
fix/bom-string-input
branch
from
August 24, 2026 17:49
95f756f to
c772787
Compare
GrahamCampbell
force-pushed
the
fix/bom-string-input
branch
from
August 24, 2026 17:56
c772787 to
2ae8145
Compare
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
1 participant
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.
Byte order marks are stripped when reading .env files but not when content is passed to the string parser, so the same bytes that load cleanly from a file throw an invalid-name error when handed to Dotenv::parse. Editors on Windows routinely prepend a UTF-8 byte order mark, and users increasingly fetch file contents themselves and parse the string. Stripping a leading UTF-8 byte order mark from string content makes the two entry points behave the same. This is stacked on #605.