Design and implement an effective error message sub-system for our .Net code generation tool

[ArthurMa1978]

We are moving fast, but our tools lack well-designed error messages. Unlike any formal compiler, which provides clear error codes and messages to help developers identify and resolve issues efficiently, we only throw exceptions with lengthy call stack information, which is very user-unfriendly.
Designing an effective error message sub-system is crucial for enhancing user experience and minimizing frustration.
The error message from our tool should be:

1. Clear and Unambiguous Messages: Ensure that error messages are simple, easy to understand, and contextually relevant. Avoid technical jargon that might confuse users.
2. Strategic Placement: Position error messages near the relevant field to make it easier for users to identify and correct the issue.
3. Provide Solutions: Good error messages not only highlight the problem but also offer solutions.
4. Avoid Blaming the User: Frame error messages in a way that doesn't place blame on the user. For example, instead of saying "You did not specify the format of the property XXX," use "Please specify the form of the property XXX".

Features

Preview Give feedback

No tasks being tracked yet.

Related tasks

Preview Give feedback

1. build(common): Update generator version in Azure SDK repo not stop when error happens autorest.csharp#2913
   v3 +1
2. [@azure-tools/typespec-csharp] Improve error message if generated property names conflict autorest.csharp#5190
   Mgmt v3 +2
   
3. Add document for all auto conversion in generator autorest.csharp#5192
   CodeGen +1
4. Enable Package validation - Part II #37826
   Mgmt +1
   
5. AutoRest Generation throws error autorest.csharp#4691
   Mgmt question +2
6. System.InvalidOperationException: Can't find Baseline contract assembly autorest.csharp#5176
   v3 +1