You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When developing in a workspace component, I've told that is a best practice to don't add the namespace suffix to any of data, in order to let the code to be deployed to any place when it's necessary.
The problem is, that doing these, makes it impossible to autocomplete anything
Steps To Reproduce:
Initialize a new project with a namespace assigned
Create a class
Try to reference it
Expected result
Autocompletion should work for both cases, trying to reference it with the namespace and without it
Actual result
Autocompletion is not working for that class, instead, you need to add the namespace.class to get it working
Additional information
VS Code Version: 1.32.3
SFDX CLI Version: 45.7.0
OS and version: Windows 10
The text was updated successfully, but these errors were encountered:
@mnunezdm I agree this is an annoying bug. While we are working on making this better, as a workaround you could temporarily set
"namespace": ""
in your sfdx-project.json file.
I had a feature request in that direction: ignore namespace configured in project.json for auto completion. but cannot find it anymore for the love of god.
Thanks for the workaround!
Summary
When developing in a workspace component, I've told that is a best practice to don't add the namespace suffix to any of data, in order to let the code to be deployed to any place when it's necessary.
The problem is, that doing these, makes it impossible to autocomplete anything
Steps To Reproduce:
Expected result
Autocompletion should work for both cases, trying to reference it with the namespace and without it
Actual result
Autocompletion is not working for that class, instead, you need to add the namespace.class to get it working
Additional information
VS Code Version: 1.32.3
SFDX CLI Version: 45.7.0
OS and version: Windows 10
The text was updated successfully, but these errors were encountered: