Codist 8.2 Beta

[wmjordan]

Download

Codist 10889

Codist 10871
Codist 10836
Codist 10833
Codist 10829
Codist 10810
Codist 10791
Codist 10787

What's New

• Syntax Highlight
  • 🆕 Allow global custom syntax highlight configuration (Is it possible to highlight built-in types by using ClassificationTypes.json and a global Codist.ct.json? #380)
  • 🆕 Prefer YAML over JSON as the custom syntax highlight configuration file
  • Fix a bug which caused semitransparent styles improperly colored (Semitransparent syntax styles without foreground color specified were incorrectly colored #385)
• Symbol Analysis
  • 🆕 Toggle buttons on menu items for command options (Suggestion: Improved Scopes for Inherited/Implemented/Extension Members #383)
  • 🆕 More filter options
  • Fix Find References command could return incomplete or excessive results in some cases
• Others
  • 🆕 New commands in Build menu to open intermediate folder
  • 🆕 Multiline Wrap-text, placeholders supported (Multi-line texts for Wrap Text feature #384)
  • Fix parentheses being improperly inserted by the auto parentheses feature

[fitdev]

Not sure if it is Codist or VS, but on the latest Stable VS (do not try Insiders 11304.161 as it has a bug that prevents loading a solution), Codist no longer underlines (apparently Github markdown does not support underline) code as per the syntax highlighter rules (even though the customize syntax highlight dialog correctly previews the style as being underlined).

[wmjordan]

@fitdev
Please show me the configuration and code and let me see what's going on.

Codist no longer underlines (apparently Github markdown does not support underline) code as per the syntax highlighter rules

[fitdev]

Here:

  extension([MaybeNullWhen(true), NotNullWhen(false)] string? s) {
    /// <summary>
    /// Returns true if <paramref name="s"/> is either <see langword="null"/>, '' empty, or has only whitespace characters.
    /// </summary>
    public bool IsBlank { [DebuggerStepThrough, MethodImpl(Const.OPTIMIZE)] get => string.IsNullOrWhiteSpace(s); }
  }

And it applies to all extension members (methods included) at both call sites and declaration sites.

Config.json.zip

[fitdev]

In fact the underline issue applies to all symbols - not just extension members, as ref structs for which I had it enabled do not show up as underlined too.

[wmjordan]

I could not reproduce the problem with your configuration.

[fitdev]

Must be some latest VS quirk then. I will see if it still happens once I get back to the normal Insiders version I was using after they issue a fix for its crash on load thing.

On a different topic - a very small feature suggestion:

Could you please support multi-line texts for Wrap Text feature. That is there should be a way to create patterns that span several lines. Perhaps character escapes like \r\n can be used (maybe with a check box as to whether they should be treated literally or as escapes).

[wmjordan]

multi-line texts for Wrap Text feature

I have posted a new issue for this request. It is not trivia thing. I will consider how to implement it when I have time.

[fitdev]

Must be some latest VS quirk then.

It does seem like it is actually a VS issue with underlines, because I just noticed that their underline reassigned variables feature does not work either. So sorry about submitting it here.

[wmjordan]

@fitdev
I've refactored underlying code of the context menu. Please help test the new beta.

[fitdev]

I will let you know if I encounter any issues :)