Blueprint

Create custom file templates for your project.

• File GitHub issues anytime you run into unexpected situations/bugs.
• Fork our project, send us PRs!

Usage

Setup where your Blueprint templates will be stored

• Create a folder anywhere in your project matching the templates path setting. By default, the path is set to blueprint-templates. (See Extension Settings if you would like to change this)

Add templates

• Create a template group by adding a new folder under the blueprint templates storage folder
• Add a template to the group by creating a new file

Create from a template

• Right click on the file or folder in the explorer
• Select "New file from template"
• Enter a name

Extension Settings

Templates Path

To change the default storage location for where Blueprint templates are stored, navigate to settings.json or ⌘, under Visual Studio Code preferences and change the blueprint.templatesPath setting

Example:

// Where your Blueprint templates are stored. Templates are loaded relative to your workspace root path. Defaults to ./blueprint-templates

Examples:
"blueprint.templatesPath": [
  "./blueprint-templates",
  "../path-one-level-up-from-workspace",
  "~/path-from-home-folder",
  "/path-from-root
]

Available Transforms

Dynamic Template Variables

Dynamic Template Variables provide template replacements at the time of file creation in addition to the standard name. The dynamic replacement token should conform to the format of {{ $<inputName> }} (we will search for a $ within {{ }}).

For each dynamic token detected, a dialog will appear during the New file from template workflow. This input will be substituted into the template at the appropriate places.

For exapmle this template:

function myFunction() {
    print("{{ $input }} comes before {{$2}} but not before {{ uppercase $input }}");
}

will show two additional dialogs. One for $input and one for $2. The same transforms that can be used on name can be used for dynamic template. Dynamic templates currently do not work within filenames.

manifest.json

You can optionally include a "manifest.json" file in your template folders. This enables a few additionally points of customization.

Examples

Example templates can be found here: blueprint-examples

We will continue to add new templates that we think may be helpful to use!

Known Issues

Release Notes

3.0.0

• Adds support for Dynamic Template Variables. You can now have multiple unique tokens within your templates that will get replaced with user input during file creation.

2.3.0

• Adds UPPER_SNAKE_CASE transform (upperSnakeCase_name or {{upperSnakeCase name}})
• Adds ability to use no transform for files names (use name token)
• Adds number of steps and current step to UI for user input

2.2.0

• Skip content replacement on files that cannot read by handlebars. Useful for non-text files like images and video.

2.1.1

Bug Fix: Fixes detection of possible overwrites on file creation.

2.1.0

Cleanup of template selection user interface; the template name is now emphasized again.

Allow templates to include hidden folders and files. System created files (Thumbs.db, .DS_Store, etc. are still ignored).

Added two new transform helpers: lowerCase and upperCase.

2.0.0

Adds ability to provide multiple folders of templates. Useful for using both a project local and a shared (global) templates.

Template folder paths also now expand ~ to the home directory.

1.5.0

Added a new transform helper: lowerDotCase!

1.4.0

Now supports non-unix paths, AKA Windows support!

1.3.0

You can now create folders and nested folder/file structures inside a template folder. Folder names inside a template folder can be templated the same way that file names are.

1.1.0

Fixes missing dependency in initial release.