Open noeldevelops opened 1 month ago
This can be a example/pattern for other error handling in the app
Docs team input and guidelines would be great for errors cc @JimGalasyn @tikimims
Example of opening logs on command: https://github.com/confluentinc/vscode/blob/6c61210b68ff1eb6ff8debb8fe433d600c9cc907/src/consume.ts#L426-L432
Code of Conduct
On what operating system are you seeing the problem?
macOS (Apple/arm64)
VS Code version
1.94.1 (Universal)
Version of Confluent extension
v0.17.x
To Reproduce
⚠️ difficult if not impossible to reproduce! (thankfully) I was forcing an error to occur locally
Current vs. Expected behavior
I expect that the error notification has specific information about what went wrong and actionable buttons to resolve it, not just "try again"
Relevant log output
Which area(s) are affected? (Select all that apply)
Project generation
Additional context
Low priority imo. This issue is very rare and hard to reproduce. It is unlikely end users will encounter this without something else going wrong before they get here.