Closed jfcherng closed 4 months ago
I remember that I had manually fixed the values for the IntEnum
s in the PR merged as https://github.com/sublimelsp/LSP/commit/c5321ad504a2060e7be466a0779544e3d72af319, but for the StrEnum
s it seems they got introduced in https://github.com/sublimelsp/LSP/commit/0ae1c7b4b4639c74d3bf688044eb428558d67d95 by adding this as the base class: https://github.com/sublimelsp/LSP/blob/fc5a7c75c8cec2e6765e218f7df980315c5c9ff3/plugin/core/typing.py#L40-L48
Related to https://github.com/sublimelsp/LSP/pull/2446#issuecomment-2059553794.
Not sure whether this is interested or not. In the LSP log panel, because we now uses
Enum
, there are enum object in the log rather than its scalar value. This disallows the payload can be formatted as JS or Python for easier reading. I know there is a website for formatting it but I've never remembered that :(E.g.,
<SemanticTokenTypes.Type: 'type'>
Example Payload