Closed jimgraham closed 7 years ago
LOL. Ummm, it's a feature? Hey @jaredpar, thoughts on this?
Hmm, the encouragement string is being displayed via ISignature::Content
. It looks like Visual Studio is treating that field as code and syntax highlighting it (in versions after 2010).
I took a look at the implementation and there is no way to disable it. Encouragement could switch to using the Documentation
property. But that ends up changing the display slightly by inserting a blank line at the top.
The blank line comes from rendering the content as empty and the documentation below it.
Hmm, right now it's not important enough for me to fix. But it seems the proper fix is not to use signatures but use adornments instead.
Adornments are probably the better route here. The biggest complication with them is getting the theme behavior correct. Which is unfortunately non-trivial
If it were trivial, it wouldn't be a Visual Studio Extension.
So true ....
I'm going to close this. If someone wants to submit a PR with an Adornment approach, I'd be all ears.
One of my "discouragements" has the word
this
in itwhen shown on top of a C# file, the discouragement seemed to have syntax highlighting. To confirm, I replaced my list of encouragements with nonsense that would syntax highlight
and they as well seem to syntax highlight.
Is this by design?