Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@peppy
Copy link
Member

@peppy peppy commented Sep 7, 2025

Closes #34929.

@peppy peppy requested a review from a team September 7, 2025 10:59
@peppy peppy added the area:import dealing with importing of data from stable or file formats label Sep 7, 2025
// if there are further troubles related to similar issues, reevaluate moving this sort of check to the import side instead (sanitising filenames on import from archive).
string destinationPath = Path.Join(mountedPath, realmFile.Filename.GetValidFilename());
string destinationPath = mountedPath;
foreach (string piece in realmFile.Filename.Split('/').Select(f => f.GetValidFilename()))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this guaranteed to be Unix path? In other words, is this correct to not be Path.GetFilenameSeparator() or whatever?

Copy link
Member Author

@peppy peppy Sep 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "guarantee" is here:

filename = filename.ToStandardisedPath();

We could probably add an assert in RealmNamedFileUsage if that makes things more palatable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:import dealing with importing of data from stable or file formats size/M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Skin files on custom folders have their names changed after external editing

2 participants