-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connect VSCode client to LspMopeServer #51
Comments
Note: #21 (comment) |
Please notify me, when you have done the first tests, connecting to the VS Code client as I would like to close #40 , once I can be sure that the implementation is correct. Any further problems concerning specific features should then become separate issues in MopeSWTP-SS21/vs-code-client. |
I have not worked on this Issue yet. |
I just connected the VsCode Client to our MopeServerJar.
I then tried After Connecting to the Server i received a Message "Hallo vom Server" and could see that the InitializationRequest was triggered. However none of the other Commands worked. So the next Step for me is to publish some Server Capabilities. |
After Publishing CompletionCapabilities, I managed to complete Something:) However there are some Major Issues:(
|
I think we need to implement the DidChangedTextDocument-Notification and DidOpenTextDocument-Notification to maintain some ShadowFiles for the Server. |
Yeah, I think you are right on track with your analysis. 👍 Keep in mind that you might have to tell the client how you want to synchronize unsaved document updates. |
After the Workaround or Fix #85 (comment) i was able to load a Model from VSCode. |
Can you double-check ...
On my machine, OMShell reports the following:
This is what I would expect, since the error is on the first token that comes after the position where the semicolon should be (6:3). Actually, now that I see the numbers... could it be that you just have a one-off error in your line and column indices? |
You are right. The Error is in fact located in 6:3.
The VSCodeClient seems to increment the received Position |
The title says it all...
Following Issues might be:
The text was updated successfully, but these errors were encountered: