MartinGC94

It's a common approach, but I wouldn't call it the best approach for writing modules because it makes the module import times slower. It's better to have a build script...

> nice module but just trying to understand what it exactly does as it might indeed improve the performance by merging all the files but doesn't resolve the "freeform input"/scope...

There's also the command specific hashtable completions which are a bit more tricky for commands to implement, see: https://github.com/PowerShell/PowerShell/issues/3845

It seems fine but I don't see a test for hiding PowerShell classes from tabcompletion: `TabExpansion2 '[hidden()] class Test1{} [Test1'` This uses the AST so it's handled differently than C#...

PowerShell was designed to have as few limitations in the command names as possible so it's not an error if someone decides to define a command called `catch` or `finally`...

@237dmitry Editors like VS code get their completion data from the PowerShell engine. This suggestion is mainly thought of to improve the editor experience, not the interactive shell experience.