Path.GetInvalidFileNameChars() is platform-dependent: on Linux it is only '/' and NUL, so a backslash in a server or character name survived sanitisation there and JournalFileTests.TheFileNameFollowsRetailsPattern failed on the Linux runner while passing on Windows. Sanitise against a fixed set (Windows' printable invalid chars plus all control chars) so one name maps to one file name on every platform. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| JournalFile.cs | ||
| JournalPage.cs | ||