search

cap-js / cds-intellij

SAP CDS Language Support for IntelliJ
https://cap.cloud.sap/docs/cds/
Apache License 2.0
12 stars 1 forks source link

[BUG] CDS syntax highlighting rarely works #80

Closed Z-AK-06 closed 3 days ago

Z-AK-06 commented 5 days ago

Is there an existing issue for this?

Current Behavior

We are several developers using IntelliJ ultimate with the SAP CDS Language Support plugin 1.3.0 on Windows 11 operating system. ~When opening / editing .cds files, most of the time no support is given at all by the plugin with regards to its documented features.~[^1] For example the syntax highlighting misses out completely, ~no documentation on mouse hovering etc.~[^1] By evidence, the reported issue in https://github.com/cap-js/cds-intellij/issues/63 also appears then.

Be aware that from time to time at a sudden the plugin appears to work without any understandable reason, but most of the time it just doesn't.

Expected Behavior

Just expecting the documented features of the plugin to be working ...

Steps To Reproduce

Just open any .cds file in the IntelliJ environment

Versions

SAP CDS Language Support for IntelliJ 1.3.0 We use a variety of patch levels of NodeJs v20, for example v20.18.0-win-x64, v20.16.0-win-x64, v20.11.0-win-x64

OS / Environment

Windows

Repository Containing a Minimal Reproducible Example

No response

Anything else?

No response

[^1]: edited, cf. https://github.com/cap-js/cds-intellij/issues/80#issuecomment-2493783611

tim-sh commented 5 days ago

Hello @Z-AK-06, can you please share the IDE logs as a first step? Regards, Tim

tim-sh commented 3 days ago

The log file sent privately by email does not seem to reveal any error. @Z-AK-06 confirmed that the other functionality mentioned was working fine after recent updates, although it remained unclear what may have caused the earlier problems. Editing the issue description accordingly.

tim-sh commented 3 days ago

@Z-AK-06 Please clarify if highlighting still seems broken.

Z-AK-06 commented 3 days ago

Hello Tim Indeed seems that the issue disappeared with the last environment update, so I am accordingly closing the present issue. Thanks for your support :-) Best regards, Andreas