feat: lg/lu editor support warning message style

[zhixzhan]

Description

Distinguish warning message and error message.

Task Item

refs #2261

Screenshots

[a-b-r-o-w-n]

There are some duplicate code paths here that I'm concerned about. Is it possible to rethink how the shell shares errors to the LU/LG fields instead of each component needing to parse/format the diagnostics?

One solution is moving the knowledge of the diagnostics into the code editors themselves because their domain is already aware of the lg/lu diagnostic.

[zhixzhan]

There are some duplicate code paths here that I'm concerned about. Is it possible to rethink how the shell shares errors to the LU/LG fields instead of each component needing to parse/format the diagnostics?

One solution is moving the knowledge of the diagnostics into the code editors themselves because their domain is already aware of the lg/lu diagnostic.

I also thought about that, accept diagnostics instead of errorMsg or warningMsg can simplify a lot usage scenarios. only if we don't want customize the message, directly show the message from diagnostics. For example, same diagnostic in inline editor show less message compare to all up view, cause form have less space.
If it's not so important to customize message, we should pass diagnostic, or further more do diagnosing in editor.

[zhixzhan]

I worked out a solution to move to pass diagnostics:

1. editor both accept diagnostics and errorMsg/warningMsg. but the display priority is errorMsg>diagnostics.errorMsg>warningMsg>diagnostics.warningMsg

2. simplify the message, use L2-L3 replace line 2 - line 3, remove the source: Main . Then the message would not be too long for inline editor. but also includes necessary information.