Frode Flaten

> I thinks really we need internal helper method in ValidateRangeAttribute to return a list of filtered strings for enum base type. Thanks. Better now?

Flaky CI. Can someone trigger rerun? :)

Can't reproduce in 7.2.5. Tested on Windows with manifest for both a loaded and unloaded module. Could you provide a minimal sample manifest?

Thanks, can repro now. It occurs only when you: - Have a `RootModule` - Use `'*'` in `FunctionsToExport/CmdletsToExport/AliasesToExport` **Workaround**: Specify `@()` or `@('your values')` in the `...ToExport` entries. It's also...

`newModuleInfo` used below is only a [shallow clone of a cached manifest](https://github.com/PowerShell/PowerShell/blob/a468fb1f499f5f6f1468571df76b50e85c9f4b39/src/System.Management.Automation/engine/Modules/ModuleCmdletBase.cs#L6237-L6240) (by filename). So it will keep adding the same tags over and over to an already populated list....

@iSazonov already on it 🙂 Found a similar issue with import while looking into it.

I think you might be remembering wrong. AFAIK this is just a string, so you'd need to use subexpression for properties. **Update:** Tested in stable and 2021.8.0. No change and...

> If {} is present it could just be replaced with $() before being sent to the evaluator. Will likely have to use AST-parsing to not break expressions with scriptblocks,...

BeforeAll is just invoked a couple of scopes above. Nothing special. You can repro the problem using: ``` & { $newVar = 123 'visible here' & { 'not here' }...

Fixed by powershell/vscode-powershell#1310, right? Will move 4 of 6 visitors to AstVisitor2 in #1886