Skip to content
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

RuntimeNamespace error #5533

Open
felfresco opened this issue Apr 11, 2024 · 5 comments
Open

RuntimeNamespace error #5533

felfresco opened this issue Apr 11, 2024 · 5 comments

Comments

@felfresco
Copy link

Summary

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

Steps To Reproduce:

  1. Create new LWC
  2. Paste this code:
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
Copy link
Contributor

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
Copy link
Contributor

@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!

Copy link

git2gus bot commented Apr 12, 2024

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

@felfresco
Copy link
Author

felfresco commented Apr 15, 2024

@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 daphne-sfdc added the status:owned by another team We are maintaining this feedback for visibility but it is not within control of our team label Apr 15, 2024
@daphne-sfdc
Copy link
Contributor

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.

@diyer diyer added area:lwc and removed status:owned by another team We are maintaining this feedback for visibility but it is not within control of our team labels Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants