Validation error not showing in VSCodium

[Ajk]

Hello,

I am currently translating a domain-specific language extension from SysML v1 to SysML v2 and I’ve encountered an inconsistency in validation behavior.

When using Syside Integrator in VSCodium, I do not see the same validation result that I see in Visual Studio Code, although I initially assumed both environments were using the same Syside extension setup.

In the screenshot, the line is flagged as an error when the applied/defined element appears to violate the annotatedElement restriction. However, in VSCodium, the same line is not flagged in the same way.

Could someone clarify what might explain this difference?

Are VS Code and VSCodium supported identically by Syside Integrator?

Could this be caused by different extension versions or different extension registries?

Is there any known difference in validation behavior between the two environments?

[Daumantas]

Hi,

LSPs in both VS Code and VSCodium are identical - the only differences may be versions. You can find versions used in the extension page, or in the log file, unless you have overridden syside.path configuration variable.

Otherwise, the diagnostic is correct because RequirementUsage is not a PartUsage. Note that before v0.9, this diagnostic was not always emitted.

[Ajk]

I checked the installed versions and found the difference: VS Code is running Syside v0.9.1, while VSCodium is running v0.8.8. Since you noted that this diagnostic was not always emitted before v0.9, the inconsistent validation appears to be version-related rather than an inherent VS Code/VSCodium difference.
Thank you so much for pointing this out.