• Fixes wrong semantic tokens for cases where a local variable is named like a different symbol

  • it's now easier to spot invalid code by looking at the semantic highlighting
    wrong type in comparison, ItMi_Gold-Instance was expected:
    
    Correct type of instance has different highlight
    

• Fixes semantic highlighting in assignment contexts
  Now it's easier to spot if a parameter or global variable/constant is being modified in an assignment
  
  

• Language Server updated kirides/DaedalusLanguageServer@7598ad1...80c4a8d
  • Introduces a simple "Go to References/Find all References" Implementation
    
  • CodeLens for Implementations and References, which shows the according numbers and allows VS Code users to click on it to see the locations.
    
  • internal preparations to support zParserExtender constructs
  • fix request panic while parsing when function parameters not yet fully declared
• implemented extension support for editor.action.showReferences - which is not directly compatible with LSP types and needs its arguments to be converted to VS Code specific elements...

Previous release introduced the possibility of Language Server deadlocks.
This release fixes those.

kirides/DaedalusLanguageServer@65ae126...7598ad1

Deprecated - Please use atleast v0.0.23

• Language Server updated kirides/DaedalusLanguageServer@3ee6716...65ae126
• semantic highlighting: it's now easier than ever to figure out if a variable is a constant, a parameter, local or some global
  coloring is depending on the used theme
  • before:
    
  • after:
    
• inlay hints
  

All settings can be toggled in VS Code settings.json

 {
   // ...
   "[daedalus]": {
        // ...
        // set this to false if semantic highlighting is not wanted
        "editor.semanticHighlighting.enabled": "configuredByTheme",
        // set this to off, or offUnlessPressed if its not wanted
        "editor.inlayHints.enabled": "offUnlessPressed",
    },
}

• Language Server updated kirides/DaedalusLanguageServer@91e0d90...3ee6716
• Code completion for nested method calls now correctly finds the right method to show the completion for and methods aswell as variables are now considered for completion items (was previously broken and only supported constants and instances)
  

• Language Server updated kirides/DaedalusLanguageServer@ab679b0...91e0d90
• Extension now contains binaries for the following os/architecture combinations
  • windows (any)
  • linux/ia32, linux/x32, linux/amd64
  • darwin/amd64, darwin/arm64
• *unix: upon starting the language server chmod +x LANGSERVER will be executed to mark the languageserver executable
• initial support for Enum/Instance annotations added
  • You can now mark javadoc parameters with {C_NPC, int, ...} or [LOG_RUNNING, LOG_SUCCESS, ...] to improve intellisense
    examples:

    • /// Creates a new log topic with the name `topicName` under the section `logSection`
      /// 
      /// @param topicName unique string used to identifiy and name the topic
      /// @param status [LOG_RUNNING, LOG_SUCCESS, LOG_FAILED, LOG_OBSOLETE] the new status
      func void Log_SetTopicStatus(var string topicName, var int status) {};
      

      

    • /// @param npc {C_NPC} the npc or any integer instance.
      func int Hlp_IsValidNpc(var instance npc) {};
      

      

You can now configure workspace settings for the language server.

example for VSCode (settings.json):

{
    "daedalusLanguageServer.fileEncoding": "Windows-1252",
    "daedalusLanguageServer.srcFileEncoding": "Windows-1252",
}

• Method documentation can now contain some javadoc to allow for parameter descriptions

• if a directory _externals\ is in the workspace, the language server looks for a _externals\externals.src or _externals\externals.d (in that order)
  • if one of these files is found, they will be parsed before user code and will be available for completion.
    Mainly useful for externals defined by Union plugins.

• DaedalusLangaugeServer updated to kirides/DaedalusLanguageServer@710c912...d86e33d
• Intellisense now sorts function parameters and local variables first
• Intellisense now has rough support for completing class/instance/prototype fields
  • this includes typed variables as well (e.g. hero, self, other, victim, ...) and local variables
• internal preparations for *unix support (conversion of filepaths from \ to os specific separators (on unix/macOS /)

• updated LanguageServer client protocol
• updated client dependencies
• DaedalusLanguageServer updated to kirides/DaedalusLanguageServer@45035dd...871d72c