Replies: 5 comments
-
Just to be clear, those are not just namespaces. Those are custom objects from other namespaces. So, they could be used, and referenced. There are at least two ways we can handle this:
Thoughts? This is related (but not identical) to #399 since these are real entities that you can reference. You get them after you invoke "SFDX: Refresh SObject Definitions". |
Beta Was this translation helpful? Give feedback.
-
I agree with your analysis. Hence I suggested to strip only(!) the namespace that is configured in one of the config json files. No way should we strip Namespaces generally. Maybe I misunderstood something? I changed the title of the issue to better reflect my suggestion. |
Beta Was this translation helpful? Give feedback.
-
Hi @Szandor72! It's been a few years, but curious to see if this is still a reoccurring issue for you? |
Beta Was this translation helpful? Give feedback.
-
Hi @Szandor72 - following up again a few years later :) Wanted to see if this still an issue or feature request you're interested in. Otherwise, we'll close this as not addressed for now. Thanks so much! |
Beta Was this translation helpful? Give feedback.
-
Generally, yes - as an opt in toggle somewhere in settings. My weighting has changed, though. It moved from "Need" to "Nice to have". I do apologize for not having followed up the first time. |
Beta Was this translation helpful? Give feedback.
-
Describe the solution you'd like
As an ISV we work with namespaces all of the time. In VS Code, if I want to use the autocomplete feature, autocompletion looks like this
Is there a way to tell VS Code or the Salesforce Extension not to use namespace?
The omitted Namespace should be the one defined in the scratch project definition or scratch config file so to avoid confusion when working on a package extension.
Beta Was this translation helpful? Give feedback.
All reactions