search

forcedotcom / salesforcedx-vscode

Salesforce Extensions for VS Code
https://developer.salesforce.com/tools/vscode
BSD 3-Clause "New" or "Revised" License
953 stars 406 forks source link

RuntimeNamespace error #5533

Open felfresco opened 5 months ago

felfresco commented 5 months ago

Summary

i have error for runtimenamespace in LWC XML e.g.omnistudio

Steps To Reproduce:

  1. Create new LWC
  2. Paste this code: <?xml version="1.0"?> 54.0 true omnistudio

Expected result

should have no error

Actual result

has an error at omnistudio

Additional information

![image](https://github.co

runtime error

m/forcedotcom/salesforcedx-vscode/assets/136463993/f0ab0827-66f0-451c-8563-85425b1a71fe)

Salesforce Extension Version in VS Code:v60.8.0

SFDX CLI Version: v60.8.0

OS and version: Windows 10 Enterprise 22H2

VS Code version: 1.87.1(user setup)

daphne-sfdc commented 5 months ago

Hi @felfresco, Is this error blocking you from deploying your LWC component to your org? If not, this would be a linting error, and you can try reloading the VSCode window (Developer: Reload Window) to restart the linter.

daphne-sfdc commented 5 months ago

@felfresco I just realized that I'm able to replicate your issue after installing the Red Hat XML extension for linting the metadata files. Yes this is a bug - sorry for the misunderstanding yesterday!

git2gus[bot] commented 5 months ago

This issue has been linked to a new work item: W-15492535

felfresco commented 5 months ago

@felfresco I just realized that I'm able to replicate your issue after installing the Red Hat XML extension for linting the metadata files. Yes this is a bug - sorry for the misunderstanding yesterday!

Hi @daphne-sfdc , any ways to resolve this bug? i need to implement an LWC in omniscript.

daphne-sfdc commented 5 months ago

Hi @felfresco, This is a bug in the LWC Language Server, which is owned by another team. We'll let you know once the other team fixes the issue.

As for workarounds, this is actually not a bug that will block you from doing LWC development. Even though you see the red squigglies, you should still be able to deploy and retrieve your LWC as expected. Just right click on the metadata file, select SFDX: Deploy This Source to Org, and you should see in the Output tab that the file was deployed successfully. Please let us know if that is not the case and/or you see any other issues.