The linting prefix was initially added in order to differentiate Cadence 1.0 errors from other errors when the appeared in VSCode/LS. However, this was probably a mistake because this is differentiatable using the "Category" and it pollutes the underlying error message.
Suggested Solution
Remove it. It should be up to consumers of the library to decide how they want to perform conditional behaviour for different categories. If they (LS) want to prefix it, then they can do so. But this should not be forced behaviour because different UIs may want to display this information differently.
Issue to be solved
The linting prefix was initially added in order to differentiate Cadence 1.0 errors from other errors when the appeared in VSCode/LS. However, this was probably a mistake because this is differentiatable using the "Category" and it pollutes the underlying error message.
Suggested Solution
Remove it. It should be up to consumers of the library to decide how they want to perform conditional behaviour for different categories. If they (LS) want to prefix it, then they can do so. But this should not be forced behaviour because different UIs may want to display this information differently.