Repository navigation
IFeedbackProvider needs a registration system on when it should be called #19364
Description
Summary of the new feature / enhancement
Currently, all FeedbackProviders will get called for every situation but we need to identify categories of when feedback can be provided. For example:
- ErrorRecrods (currently implemented)
- nativecommand non-zero exit code (IFeedbackProvider can't work against native commands on non-zero exit code #18852)
- comments (ChatGPT type integration)
- successful execution (Feedback can provide tips on doing things better)
There may be other scenarios and some FeedbackProviders may support multiple scenarios.
Proposed technical implementation details (optional)
Probably need an enum and have each IFeedbackProvider implementation declare what it supports
Activity
microsoft-github-policy-service commentedon Nov 15, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 15, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 15, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 22, 2023
This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.