-
Notifications
You must be signed in to change notification settings - Fork 406
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
Manifest Editor #959
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Not familiar with how this platform works. But this feature would be invaluable for system admins who are not familiar with the API. |
Something I've found really useful with my package builder is the ability to point it at a collection of source files and have it define the required package.xml for them. E.g.
Some of those use cases are more specific to relying on the metadata API to do the deployments. Could your editor provide direct links out to the applicable source files? E.g. Open class X in the editor. |
I think even for developers it would be invaluable. I'm currently trying to generate a package.xml containing all reports, but because the Report type does not support the * wildcard I have to generate this manually. This is probably the main feature holding us back from switching to SFDX - a definite must-have from us before the Force.com IDE is retired. |
This is being replaced by #862 |
Currently, in VS Code working with the org development model requires manually editing package.xml files. In order to improve the experience we could build a UI that enables quicker visual editing of package.xml files similar to what exists in other tools like the Force.com IDE.
Below are some rough mockups of how this might be implimented using the VS Code web view extensibility.
The text was updated successfully, but these errors were encountered: