You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to be able to have some user-defined comment tags participate in code analysis, such that certain tagged comments can produce either warnings or errors.
So, at the basic level, a 3rd dropdown is needed on tags section in the Syntax Highlight Configurations called Analyzer (or something similar) with values:
None: Does not participate in code analysis at all
Warning: If tag is present a compiler warning is issued
Error: If tag is present, it's a compile time error
Maybe for Warning and Error add ability to define custom, per-tag analyzer IDs.
A More Advanced Version:
To make this even more useful, whether or not a Warning/Error is issued can be made to depend on not just on the comment tag itself (string value), but on additional conditions:
Project configuration / compile time #constant
Date - to enable reminders / todo-like functionality
To implement it as an Analyzer in an extension, you can look into how they do analyzers in Roslynator
The text was updated successfully, but these errors were encountered:
You are right! Sorry about that. I guess I forgot to keep the 2 lists in sync (I have more comment tags defined in Codist than I have defined in VS's task list).
It would be nice to be able to have some user-defined comment tags participate in code analysis, such that certain tagged comments can produce either warnings or errors.
So, at the basic level, a 3rd dropdown is needed on tags section in the Syntax Highlight Configurations called Analyzer (or something similar) with values:
Maybe for Warning and Error add ability to define custom, per-tag analyzer IDs.
A More Advanced Version:
To make this even more useful, whether or not a Warning/Error is issued can be made to depend on not just on the comment tag itself (string value), but on additional conditions:
To implement it as an Analyzer in an extension, you can look into how they do analyzers in Roslynator
The text was updated successfully, but these errors were encountered: