Creating a PowerShell 7.4 Feedback Provider
summary
Experimental PowerShell 7.4 feedback providers register a C# interface but can be written with the provided ScriptFeedbackProvider module in PowerShell; they inspect the AST and last error, return structured suggestions, and must finish in about 100 milliseconds so local caches are required. Example: a shipped command‑not‑found fuzzy suggester exists and the author ships MGAQDetect to detect missing Microsoft Graph advanced‑query flags (consistencyLevel=eventual, $count), it registers at import and works in a regular console (not yet in VS Code host).
AI-written summary · about
chapters (11)
- 0:00PowerShell 7.4 feedback providers
- 1:52Why use feedback providers
- 7:32Feedback provider architecture
- 16:41Demo: command not found provider
- 21:57Script analyzer overlap
- 26:47ScriptFeedbackProvider module
- 35:17Live demo: creating provider
- 41:12Long scripts and error handling
- 1:05:06Troubleshooting feedback providers
- 1:17:28Registering in C# modules
- 1:27:17Q&A
related talks
39mShell Enhancements
43mPowerShell Tooling
01h 14mCreating a PowerShell Editor
45myear of improvements to your PowerShell editing experience
01h 32mOptimizing Visual Studio Code for PowerShell, 2023 Edition
44mUsing Visual Studio Code as Your Default PowerShell Editor
45mTake your PowerShell to the next level with error handling and debugging
30mPokekYoke Mistake-Proofing your PowerShell scripts and functions