-
Notifications
You must be signed in to change notification settings - Fork 404
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Unified Create from Template Experience #901
Comments
Minor
I think we were asking for an VS Code API to at least get the full path to the resource but that was |
We wouldn't show anything. The assumption here is that if a user is using custom names (which is technically allowed, but really doesnt work that well in VS Code) they are an advanced user and will use the command+p menu item which will show all the template and then ask them where they want to create it.
I think we can show the aura components on any subfolder.
yes, this is the solution to that nevered issue which they wont do. That issue would allow us to filter when a command is shown in the tree, but that isnt needed anymore with this solution. The command would be a single command and always the same, but once the command is run we do know the path so we can filter the templates that are shown based on that path context. |
Thank you for filing this feature request. We appreciate your feedback and will review the feature at our next grooming session. We prioritize feature requests with more upvotes and comments. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Today, we provide individual commands for creating each different kind of template as well as right click menu items for every create experience. This has started to become unwieldy for several reasons:
SFDX: Create Visual Force Page
on every folder in the entire project.The proposed solution is to simplify the creation of any source into a single command that provides options. The command would be
SFDX: Create From Template
. It would be exposed in the command pallet and the right-click menu on all folders in a project.When a user runs the command by right-clicking a folder, we should have a context as to where that command originated. As such we will present a list of templates to the user based on the folder selected. We will use the default folder locations of metadata to filter that list. So for example, if they run the command from the
classes
folder they would be presented with a list of apex class templates to create.The UI to pick classes would initially be the built-in visual studio picker UI, but could eventually evolve into a more advanced custom template UI.
From an implementation standpoint this would also mean that each salesforce extension would no longer expose its own create commands. We would have a single create command exposed from the core extension. Thus ensuring a completely consistent experience no matter which type of source is created.
The text was updated successfully, but these errors were encountered: