Fix Windows export paths for invalid contact names - #2
Open
1uxury 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.
This fixes export failures on Windows when a contact remark contains characters that are invalid in file or directory names, such as ?, *, :, <, >, |, or trailing spaces/dots.
The fix sanitizes contact remarks only when they are used in export paths, while keeping the original remark unchanged in chat content and UI display.
It also handles Windows reserved device names such as CON, NUL, COM1, and LPT1.
Tested with a contact remark containing an invalid Windows filename character.