Go CodeGen should provide clear message for self-service trouble shooting #1484
Labels
design-discussion
An area of design currently under discussion and open to team and community feedback.
Milestone
We need to empower our internal customer to easily trouble shooting and fix spec issues that would block the CodeGen.
This will also be helpful for external customer in the future
If certain TypeSpec features or patterns are not supported by CodeGen, we should clearly point it out and suggest them to update the spec with the features we supported for CodeGen.
Today, Go CodeGen just returned a big call-stack like below which will be difficult for self-service resolving the problem.
I suggest we improve the following areas:
The error reported today: (copied from #1465 (comment))
The text was updated successfully, but these errors were encountered: