Closed sigmaaa closed 3 months ago
The changes primarily focus on integrating Language Server Protocol (LSP) support into the Espressif IDF core and UI bundles. Dependencies on LSP-related bundles were added to the core, while redundant dependencies were removed from the UI. Additionally, a new LspService
class was introduced to manage LSP servers, and existing methods in LaunchBarListener
were refactored to utilize this new service.
Files | Change Summary |
---|---|
bundles/com.espressif.idf.core/META-INF/MANIFEST.MF |
Added dependencies: org.eclipse.cdt.lsp.clangd , org.eclipse.cdt.lsp , org.eclipse.lsp4e . |
bundles/com.espressif.idf.core/src/com/espressif/idf/core/build/... |
Added LspService import, created LspService instance, updated options, restarted LSP servers. |
bundles/com.espressif.idf.core/src/com/espressif/idf/core/util/... |
Introduced LspService class to manage LSP servers and configurations. |
bundles/com.espressif.idf.ui/META-INF/MANIFEST.MF |
Removed dependencies: com.espressif.idf.lsp , org.eclipse.lsp4e ; retained org.eclipse.cdt.lsp.clangd . |
bundles/com.espressif.idf.ui/src/com/espressif/idf/ui/LaunchBar... |
Removed LSP-related imports and methods, replaced with LspService methods. |
sequenceDiagram
participant User
participant LaunchBarListener
participant LspService
participant LSPServer
User->>LaunchBarListener: Initiate Build
LaunchBarListener->>LspService: restartLspServers()
LspService->>LSPServer: Restart
LSPServer->>LspService: Confirm Restart
LspService->>LaunchBarListener: Servers Restarted
LaunchBarListener->>User: Build Completed
In the realm of code so bright, LSP servers take flight. Dependencies align, new paths we find, With
LspService
, all in kind. Code anew, with ease and grace, Espressif's build, a smoother pace.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
@sigmaaa hi!
Tested under: OS - Windows 10 ESP-IDF: v5.2.1
build project -> check additional lsp options -> --compile-commands-dir points to the right path ✔️ change the target -> check query drivers -> points to correct toolchain ✔️ Also verified with custom build folder ✔️
Since we have it as a default, should we remove this hint ?
Hi @AndriiFilippov We can remove troubleshooting from the build console and move it to clangd documentation area
Description
Set --compile-commands-dir= for the current project which the user is trying to build
Fixes # (IEP-1246)
Type of change
Please delete options that are not relevant.
How has this been tested?
Test A: build project -> check additional lsp options -> --compile-commands-dir points to the right path Test B: change the target -> check query drivers -> points to correct toolchain
Test Configuration:
Dependent components impacted by this PR:
Checklist
Summary by CodeRabbit
New Features
Refactor
LspService
methods for better functionality.