Global blueprint folder?

[stewartduffy]

First up this is awesome. Exactly what I was looking for.

One niggling thing - is there any away to define blueprint dir outside of the workspace scope? So could I define 1 folder of blueprints & have all my spaces use them?

[reesemclean]

This is definitely something I’ve thought of but not tested; I wonder if setting a relative path for the blueprint.templatesPath would work? Even if that works, a better implementation something like that, I’m thinking you’d need to register a path (or paths?) in the settings file where it would look for an additional folder(s). Then when you try to create from template there would be sections for each path. Sound like what you would imagine?

…

On Apr 8, 2018, at 8:08 PM, Stewart Duffy ***@***.***> wrote: First up this is awesome. Exactly what I was looking for. One niggling thing - is there any away to define blueprint dir outside of the workspace scope? So could I define 1 folder of blueprints & have all my spaces use them? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[stewartduffy]

I tried using the following:

"blueprint.templatesPath":"~/repos/some_folder_outside_current_space/"

No Luck. The url then resolves & errors to:

path_to_current_workspace/~/repos/some_folder_outside_current_space/.

So it looks the current workspace path is always prepended to the path you set. My current work around is adding a symlink to the workspace folder to my templates.

[reesemclean]

Version 2.0.0 has just been released. It supports multiple folder paths and will now expand "~" to your home directory!

[reesemclean]

Let me know if you have trouble getting it setup with the new changes.