Normalize RECORD paths when writing - #353
Open
PNHD wants to merge 1 commit into
Open
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
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.
Fixes #158.
RecordEntry.to_row()currently normalizes backslashes only when running on Windows. ARecordEntrycan also contain a path read from a Windows-generated RECORD while installer itself is running on another platform, so the serialized path must be normalized independently of the host OS.Normalize backslashes to forward slashes unconditionally in
to_row(), matching the existing normalization performed when parsing RECORD rows.A regression test constructs a Windows-style path and verifies that
to_row()emits a forward-slash RECORD path on every platform.Validation:
9ef6a9f