confluentinc / confluentinc/vscode

Incorporate `unhelpfulReason` once exposed from the VS Code API

Open
#1,748 0 comments 0 reactions 3 assignees Claimed by @shouples View on GitHub
Copilot external on hold
Dominant language
TypeScript
Stars
34
Forks
17
Avg merge
1d 22h
Merged PRs (30d)
8

Description

While debugging the `ChatResultFeedback` interface, we see this `unhelpfulReason` property that's always `undefined`:
![Image](https://github.com/user-attachments/assets/17a8b740-3826-448a-874f-f1c0951c92e1)

But it isn't shown anywhere in here: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/3ca0d1b418a6010d566513a85f4831372d1b839a/types/vscode/index.d.ts#L19511-L19540

If VS Code exposes this for extension development, we should include it in our telemetry flow.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.