Manifest Editor

[ntotten]

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.

[mikeflemingcfs]

Not familiar with how this platform works. But this feature would be invaluable for system admins who are not familiar with the API.

[FishOfPrey]

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.

1. here is a folder of source files, create a package for it.
2. here is an existing package.xml file, add this additional source file to it.
3. scan the folder for source files that have changed past a certain date and create a package from them.

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.

[ghost]

Not familiar with how this platform works. But this feature would be invaluable for system admins who are not familiar with the API.

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.

[ntotten]

This is being replaced by #862