Infinite name thing:
For example, the name of the script is called “Testing”
and you put --$Testing script$ at the top, it continuously adds to the script, and it should clear the script and add the template instead of adding it onto the script, or have it be toggleable.
Edit: other than that this is really useful.
I designed it so that it doesn’t clear the script when inserting a template. With this you have more options on what to do. You can either select everything and replace it with --$TemplateName or you could add it somewhere else in a script like this.
It would be nice to have a clearing a setting that you set like in the script you will put in the script that you put the template in, did that make sense? I’ve got no clue.
I have released a new update that adds this functionality. Using --$TemplateName will continue using the old way, while --$$TemplateName will replace the entire script.
Oh. I went through this before and didn’t realize how actually useful this is for module building. This is such a good resource, thanks I’ll be sure to try it :), are there any already existing templates?
I don’t think this is handled correctly currently. I might fix this in an update sometime, but it’s not a priority right now because it seems like something that will never happen.
In a future version of Code Templates I plan to add a way to export templates that you’ve created to share with other users. Right now you can only import templates. The import codes can be used by right clicking “+ Add” and selecting import. For example, by using the Knit import code some Knit tenplates are added (KnitService, KnitController, and KnitComponent).