You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Cairo ecosystem has evolved, and the language server is now included in Scarb, the package manager for Cairo projects. This new language server needs to be supported in mason-lspconfig.
Describe the solution you'd like
Rename the current Cairo LSP to cairo_1_ls to maintain backward compatibility for Cairo 1.0 projects.
Add support for the new Cairo language server that's bundled with Scarb.
Implementation Suggestion
Since the language server is now part of Scarb, and Scarb is required to run Cairo projects, we could:
Add a script that fetches the language server directly from Scarb.
Implement a similar logic to what's done in the Cairo VSCode extension for detecting and using the Scarb-bundled language server.
Benefits
Ensures up-to-date language server support for the latest Cairo versions.
Maintains compatibility with older Cairo 1.0 projects.
Aligns with the current Cairo ecosystem tooling.
Describe potential alternatives you've considered
No response
Additional context
The Cairo VSCode extension might serve as a reference for implementation details: Cairo VSCode Extension
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The current Cairo LSP supported by mason-lspconfig has been archived (it only supports Cairo 1.0) and is no longer maintained: https://github.com/ericglau/cairo-ls
Problem
The Cairo ecosystem has evolved, and the language server is now included in Scarb, the package manager for Cairo projects. This new language server needs to be supported in mason-lspconfig.
Describe the solution you'd like
cairo_1_ls
to maintain backward compatibility for Cairo 1.0 projects.Implementation Suggestion
Since the language server is now part of Scarb, and Scarb is required to run Cairo projects, we could:
Benefits
Describe potential alternatives you've considered
No response
Additional context
The text was updated successfully, but these errors were encountered: