Comments (12)
Hi @Amit-Tripathi @eriksinnard, I spoke with my team and CLI Team, and we believe the org browser is working as expected. The reason the components in managed packages are not visible in org browser is that they shouldn't be retrieved - they're able to be used but users aren't supposed to see their code and thus we would have to figure out how to implement this limited visibility to make the components read-only.
That being said, your issue is a very common feature request, and we do agree that we haven't added adequate support for package-based development across a number of our features. Given the recent uptick of this issue across IDEx and CLI Teams, we'll be revisiting this in our next planning session.
Thank you for your patience, and we'll keep you in the loop with any updates.
from salesforcedx-vscode.
@daphne-sfdc That sounds great, thank you for the update! Don't hesitate to reach out if we can provide any additional context or feedback.
from salesforcedx-vscode.
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.
from salesforcedx-vscode.
Hello @Amit-Tripathi π It looks like you didn't provide all the required basic info in your issue.
If you haven't already, please provide the following info:
Salesforce Extension Version in VS Code:
Salesforce CLI Version:
OS and version:
VS Code version:
Most recent version of the extensions where this was working:
Here's an example of a set of required info that will pass the validation:
Salesforce Extension Version in VS Code: 60.13.0
Salesforce CLI Version: @salesforce/cli/2.42.6 darwin-arm64 node-v18.18.2
OS and version: MacOS Sonoma 14.5
VS Code version: 1.89.1
Most recent version of the extensions where this was working: 60.11.0
A few more things to check:
- Make sure you've provided detailed steps to reproduce your issue, as well as all error messages that you see.
- A repository that clearly demonstrates the bug is ideal.
- Error messages can be found in the Problems Tab, Output Tab, and from running
Developer: Toggle Developer Tools
in the command palette.
- Make sure you've installed the latest version of the Salesforce Extension Pack for VSCode. (docs)
- Search GitHub for existing related issues.
Thank you!
from salesforcedx-vscode.
Hello @Amit-Tripathi π Have you tried updating to the latest version of the Salesforce Extension Pack?
Latest: 61.1.2
We suggest you to update to the latest version of the Salesforce Extension Pack in the VSCode Extensions view and confirm that you're still seeing your issue.
from salesforcedx-vscode.
Salesforce Extension Version in VS Code:61.1.2
Salesforce CLI Version:@salesforce/cli/2.46.6 darwin-x64 node-v20.11.1
OS and version:MacOS Sonoma 14.5
VS Code version:1.90.2
Most recent version of the extensions where this was working:N/A
This issue was reported on my behalf - the requested version details are above.
from salesforcedx-vscode.
Hi @eriksinnard, thanks for creating the issue. I was wondering if you tried refreshing the org browser (Open Command Palette > Run command SFDX: Refresh Types
). There's a current issue with duplicated namespaces in Org Browser, but at least they show up. I'm curious on why you don't even see the metadata. For example I see it like this
from salesforcedx-vscode.
@CristiCanizales I performed a refresh using the refresh button in the org browser and using the SFDX: Refresh Types command at the command palette and I still do not see any namespaced components in the org browser.
I tried this against all of the org types I have access to; scratch orgs, sandboxes, and trialforce production orgs and I see the same behavior.
To eliminate any issues with local configuration, I set up a new SFDX project in a Salesforce CodeBuilder instance and connected to a default org with several managed packages installed. In all of these cases, I still do not see any managed components in the org browser.
Please let me know if I can provide any additional detail.
Thanks!
from salesforcedx-vscode.
@daphne-sfdc that is an excellent point when it comes to managed components containing code. I used Apex Classes in my testing to correspond with @CristiCanizales example, but in the real world I wouldn't expect the org browser or the CLI to return the code of an apex class/VF page/Aura Component/LWC. So where those components are concerned I totally agree with your analysis.
Where components are managed but can still be modified or extended by subscribers is truly the use-case we're hoping to address. As an example, all our subscribers add custom fields to our managed objects, but because the managed objects do not show in the org browser, interacting with these components becomes more difficult.
I was expecting that this recent PR would update the functionality to expose managed components such as custom objects, flexipages, layouts, etc in the org browser, which would be extremely useful for a lot of our internal teams and our subscribers. With the additional context of this discussion I wonder if this PR was focused on exposing namespaced components from unlocked packages but still excluding namespaced components from managed packages? I'm inclined to think that may be why @CristiCanizales and I were seeing different behavior.
from salesforcedx-vscode.
With the additional context of this discussion I wonder if this PR was focused on exposing namespaced components from unlocked packages but still excluding namespaced components from managed packages? I'm inclined to think that may be why @CristiCanizales and I were seeing different behavior.
Yes, the example that @CristiCanizales provided above is with an unlocked package - from investigating this issue we realized that namespaced components from managed and unlocked packages are treated differently, and rightfully so.
Where components are managed but can still be modified or extended by subscribers is truly the use-case we're hoping to address. As an example, all our subscribers add custom fields to our managed objects, but because the managed objects do not show in the org browser, interacting with these components becomes more difficult.
We did not consider this use case, but now that you mention it, it makes sense why you would want managed components to be visible in the org browser and why this is such a popular feature request. Our team will be talking about how we want to implement this during our planning.
from salesforcedx-vscode.
Related Issues (20)
- Using Rename Symbol (F2) in VSCode renames also part after dot. HOT 2
- π’ π’ Einstein for Developers enters the Salesforce Extension Pack (Expanded) with release 60.15.0 of the Expanded Pack HOT 3
- unable to connect org HOT 2
- Run Query Option Above SOQL Queries with Results in SOQL Builder Table View HOT 2
- Salesforce Extension Pack (Expanded) has incorrect publisher for Apex PMD extension HOT 3
- Apex debugger not showin Variables HOT 3
- Added an extension setting item that allows you to show or hide the "sf.delete.source.current.file" command in "editor/context" in the salesforcedx-vscode-core package from the context menu. HOT 2
- Running SFDX: "Deploy Source to Org" in VS Code deploying takes too long (15-20 mins) to complete. HOT 2
- Running SFDX: "Deploy Source to Org" in VS Code deploying takes too long (15-20 mins) to complete HOT 5
- Support for newer Java version HOT 7
- Cannot deploy namespaced Apex classes in unlocked packages to org HOT 10
- Infinite Activation HOT 3
- Doesn't work on Macbook M2 chip. HOT 3
- sfdx authorize an org failed to run HOT 2
- Timeout or long time for retrieve and diff functions HOT 15
- Repeated IllegalStateException on Valid Apex Code Using Apex Language Server HOT 4
- π£Important Notice: Errors Caused by Recent Upgrade of ESLint Extension HOT 1
- Quick Start LWC development article out of date HOT 3
- Cannot read properties of undefined (reading 'entries') HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from salesforcedx-vscode.