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
I added a pact-lsp client to support the pact-lsp server in the Pact for Visual Studio Code (vscode) extension (kadena-community/pact-vscode@916d4c0)
I used a sample lsp extension for vscode and it does work for the functionality show in the screenshots for pact-lsp: completes and hovers for enforce-* , is-charset , read-* , mod, define-* , ..
But some pact keywords appear to be unknown to pact-lsp, some I tested but probably not a complete list: module, defcap, defun, defconst, defschema, deftable, defpact, step, let, let*, property. These are not found for completion and not showing the docs on hover.
My impression is that this is an issue at the lsp server level rather than with the lsp client I added to the pact extension.
This is the debug output when typing (module ) and hovering it:
I added a pact-lsp client to support the pact-lsp server in the Pact for Visual Studio Code (vscode) extension (kadena-community/pact-vscode@916d4c0)
I used a sample lsp extension for vscode and it does work for the functionality show in the screenshots for pact-lsp: completes and hovers for enforce-* , is-charset , read-* , mod, define-* , ..
But some pact keywords appear to be unknown to pact-lsp, some I tested but probably not a complete list: module, defcap, defun, defconst, defschema, deftable, defpact, step, let, let*, property. These are not found for completion and not showing the docs on hover.
My impression is that this is an issue at the lsp server level rather than with the lsp client I added to the pact extension.
This is the debug output when typing
(module )
and hovering it:The text was updated successfully, but these errors were encountered: