Replies: 1 comment 1 reply
-
|
hey @Ztrizzo , I just realized from your post that the command was broken, fix: salesforcecli/plugin-org#1529 These are the supported types: So we are missing apex triggers, lwc/aura components and email templates/reports. would you mind sharing the specific section in the org (url or setup section) you expect for each metadata? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, the --source-file flag for the sf org open command only supports Flow metadata types. This is a very useful feature for quickly navigating from a local source file to the corresponding record in a Salesforce org, but it would be even more powerful if it supported additional metadata types.
For example:
Apex classes and triggers
Lightning Web Components (and Aura components)
Custom objects, fields, and validation rules
Email templates and reports
Being able to open these directly from their local source files would streamline development and debugging workflows, especially when working in large repositories with mixed metadata.
Beta Was this translation helpful? Give feedback.
All reactions