{"version":"2.1.280","anchor":"windows-path-safety-check-now-returns-a-reason-code-instead","canonical_anchor":"windows-path-safety-check-now-returns-a-reason-code-instead","heading":"Windows-path safety check now returns a reason code instead of a boolean","tier":"internal","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/windows-path-safety-check-now-returns-a-reason-code-instead","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Windows-path safety check now returns a reason code instead of a boolean\n\nWindows path-safety checks now report a specific reason instead of just true or false\n\n**What**\n\nThe function that checks whether a file path is unsafe on the current platform now returns a specific reason code instead of a plain true\/false. Possible reasons include `nt_device_namespace`, `colon_past_drive_position`, `tilde_digit`, `device_path_prefix`, `trailing_dot_or_whitespace`, `dos_device_suffix`, `dot_run_segment`, and `unc_or_webdav_form`.\n\n**Why**\n\nKnowing the specific reason a Windows path was flagged as unsafe, rather than just that it was, allows more precise handling or messaging around path validation, particularly for Windows-specific quirks like device namespaces and reserved path forms.\n\n- Area: Windows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}