Ideas to improve extensibility about templater HOT 3 CLOSED

Hey, thanks a lot for the feedback !

I completely agree with all of your ideas, and i will use this post to explain what are my ideas for the future of this plugin.

For the arguments, i had the same exact idea. I think in the future users will be able to pass a list of args to the internal template, and i will pass that list to the internal template function handling this. This will allow internal templates to be way more dynamic. Thanks for the code, that will come handy when i develop this functionality !

Your idea of being able to call some local javascript files is very interesting, and could make this plugin way more scriptable than what it is in its current state. I'll keep this idea in mind for the future.

Concerning the internal templates, I don't think the current way to add new internal templates is really extensible and sustainable. This plugin is really in a beta state and I will probably refactor the way internal templates can be added later.
I was thinking of maybe declaring an interface, where one would have to create a class that extends this interface in order to develop a new internal template.

For the prefixed tags, they are indeed to prevent conflicts with user defined tags, and to recognize internal templates easily. I could maybe change this to something shorter in the future.

For the internal_templates_map, I added the mustaches here because I don't want them to be mandatory, if someone wants to develop a new internal template that can be matched with the tag [[<template>]], they can.

from templater.

I think with the new version, this issue can be closed. Nice work @SilentVoid13!

from templater.

First, massive thanks for your great work on this plugin @SilentVoid13 and to @liamcain for the calendar and periodic notes plugins. My primary use is to combine these for daily, weekly, and quarterly note templates.

I'm attempting to create a "pretty" date title for my notes generated from the templates, but the note won't always be generated from the template on the same day as the note. (e.g. if I'm planning my day the night before). Is there something I'm missing where that info would be exposed?

Along these lines, what are your thoughts on adding environment variables containing metadata of the new note, workspace, vault, and front-matter.

If I can find some time I'll spike this and send a pull request to review, but wanted to get your thoughts first in case I'm barking up the wrong tree.

from templater.