-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
VSCode and LSP does mark errors in 2.5.0.M2/M3 #141
Comments
I can confirm it's not working in 2.5 M3 |
Since the extension didn't change i would say that something in openhab core did change. |
Do I have to open a issue there and link it with this one? |
Would make sense to me, yes. We can leave this one open and see if there is something to do from vscode side. |
No movement on issue 1030, would it be polite to ask somebody directly there, and who. |
I didn't expect any movement that fast to be honest. I have tried todig into this topi too, but it is not that self explaining (at least to me). I am back from vacation and will try to push some things forward now, but cant promise anything. |
Thanks, I plan to move to new JSR232, Jython, but still, have a lot of old-style rules. |
I would love to see support for it. :) |
I am optimistic now and will close this one since openhab/openhab-core#1171 has been merged. 🙂 |
I migrated my 2.4.0 production docker installation to 2.5.0.M2.
I realized that from that point on VSCode did not mark error in rule file.
I created on my test system 2 empty docker installations with 2.4.0, 2.5.0.M2, 2.5.0.M3.
I edited a simple "test.rules" file with a rule containing errors (missing items)
On version 2.4.0.
on versions 2.5.0.M2/M3:
and all version following workspace setting:
I set the debug to trace
log:set TRACE org.eclipse.smarthome.model.lsp log:tail 14:23:26.905 [INFO ] [del.core.internal.ModelRepositoryImpl] - Refreshing model 'test.rules' 14:23:33.330 [DEBUG] [rthome.model.lsp.internal.ModelServer] - Going to wait for a client to connect 14:23:33.332 [DEBUG] [rthome.model.lsp.internal.ModelServer] - Client /192.168.3.41:63511 connected
The text was updated successfully, but these errors were encountered: