Get-DbatoolsError: Use FullyQualifiedErrorId to filter $global:error

[andreasjordan]

Type of Change

• [x] Bug fix (non-breaking change, fixes # )
• [ ] New feature (non-breaking change, adds functionality, fixes # )
• [ ] Breaking change (affects multiple commands or functionality, fixes # )
• [ ] Ran manual Pester test and has passed (.\tests\manual.pester.ps1)
• [ ] Adding code coverage to existing functionality
• [ ] Pester test is included
• [ ] If new file reference added for test, has is been added to github.com/dataplat/appveyor-lab ?
• [ ] Unit test is included
• [ ] Documentation
• [ ] Build system

Maybe it's only my system, but the ScriptStackTrace does not contain "dbatools". I think it's because the commands are not imported from a file but a compressed file.

But "dbatools" is present in the FullyQualifiedErrorId. So we should use this.

Or is there a better way to filter?

[andreasjordan]

The test passed in the past because of the way the tests import the module: They use the file by file method, so the filename and thus "dbatools" is part of the stack trace...

[potatoqualitee]

ah ha! appreciate the pr