Does -execludePaths Block Subdirectories?

[Sn3akyP3t3]

I pulled down the repo and added to the Unit Test a scenario that seems to pass, but when using it via CLI in pwsh I'm seeing files that should have been excluded are actually included and I'm curious if its just not supported or my CLI syntax is wrong.

This is what I added to the Unit Test

private static string TestFile7 => Path.Combine(InputRoot, "ProjectB", "obj", "Debug", "net8.0", "Assembly.cs");

// Added to the list
private readonly string[] TestFiles =
    {TestFile0, TestFile1, TestFile2, TestFile3, TestFile4, TestFile5, TestFile6, TestFile7};

// Added to the testing data row
[InlineData(new[] { "**/bin", "**/obj", "**/ Debug", "Properties" }, new[] { 0, 1, 4})]

This were the attempted commands used:

puml-gen ./ ./../PumlStuff -dir -execludePaths **/bin,**/obj,**/Debug,**/Properties,**/net8.0 -createAssociation -AllInOne
puml-gen ./ ./../PumlStuff -dir -execludePaths "**/bin, **/obj, **/Debug, **/Properties, **/net8.0" -createAssociation -AllInOne
puml-gen ./ ./../PumlStuff -dir -execludePaths "**/bin,**/obj,**/Debug,**/Properties,**/net8.0" -createAssociation -AllInOne

They all seemed to include the files in the directory that was undesired:

...OtherFiles...
Processing "./obj\Debug\net8.0\.NETCoreApp,Version=v8.0.AssemblyAttributes.cs"...
Processing "./obj\Debug\net8.0\ProgramName.AssemblyInfo.cs"...
...OtherFiles...

Is my use of -execludePaths correct or should I be formatting it differently? The Unit Test I added indicates it should work, but I can't seem to get it to agree. Perhaps its because I'm using Beta 5 and not Beta 6? I'll try to build locally and install from local and try again at another time.