PR Summary

This PR fixes the issue where -Qualifier:$false, -NoQualifier:$false, -Leaf:$false, and -IsAbsolute:$false are not respected in Split-Path, causing them to behave the same as their $true counterparts.

Fixes #26470
Related to #25242

PR Context

When these switch parameters are explicitly set to $false for Split-Path, the cmdlet incorrectly behaves as if they were set to $true. This occurs because the code uses ParameterSetName (a string) in a switch statement instead of checking the actual boolean values of the switch parameters.

This fix converts the switch statement to an if-else chain that directly checks each switch parameter's boolean value, ensuring that explicit $false values are properly respected.

Changes

• Modified ParsePathCommand.cs: Converted the switch statement to an if-else chain that checks the actual boolean values of -IsAbsolute, -Qualifier, -Leaf/-LeafBase/-Extension, and -NoQualifier
• Added 4 test cases in Split-Path.Tests.ps1 to verify each switch parameter respects :$false

Testing

• Added new tests for explicit :$false parameter handling:
  • "Should handle explicit -Qualifier:`$false parameter value correctly"
  • "Should handle explicit -NoQualifier:`$false parameter value correctly"
  • "Should handle explicit -Leaf:`$false parameter value correctly"
  • "Should handle explicit -IsAbsolute:`$false parameter value correctly"
• Each test verifies that when the switch parameter is set to $false, the cmdlet falls back to default behavior (returning the parent path)
• Pre-fix: All 4 new tests fail
• Post-fix: All 4 new tests pass
• All 11 existing tests continue to pass

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge. If this PR is a work in progress, please open this as a Draft Pull Request and mark it as Ready to Review when it is ready to merge.
• Breaking changes
  • None
• User-facing changes
  • Not Applicable
    • This fix corrects incorrect behavior to match expected behavior; no documentation changes needed
• Testing - New and feature
  • Make sure you've added a new test if existing tests do not effectively test the code changed