Currently Wingman is setup to throw when invalid configuration scenarios are detected. The original intent was to prevent the user going to Chat and it being unresponsive.
since we have evolved Wingman to have a config pane we can no longer fail the extension, consider removing throw and maybe enhance the existing error state so the config screen still loads
also consider the state of the extension when it does fail to start up. We probably want to consider hiding quick fix/code action options - or on use have them emit an error dialog. Same with chat or load a chat shell that indicates it’s not loaded properly.
RussellCanfield
commented
7 months ago
Currently Wingman is setup to throw when invalid configuration scenarios are detected. The original intent was to prevent the user going to Chat and it being unresponsive.
since we have evolved Wingman to have a config pane we can no longer fail the extension, consider removing throw and maybe enhance the existing error state so the config screen still loads
also consider the state of the extension when it does fail to start up. We probably want to consider hiding quick fix/code action options - or on use have them emit an error dialog. Same with chat or load a chat shell that indicates it’s not loaded properly.