More Configuration for Templates

[bburgess19]

Custom Directories and note_id_funcs for templates

This PR implements the features discussed by #165.

In short, it:

1. Allows notes created using templates to automatically be placed in a specific directory
2. Allows such notes to have their own note_id_func for naming themselves specially

Testing the Behavior

1. Create a template and put it in the template folder

• For this example, I'm using "zettel" as the template ID

2. Create a configuration for that template, example:

--[[ In configuration ]]
templates = {
  customization = {
     zettel = {
       dir = "existing/path/to/directory,
       note_id_func = function(title)
         return "my-cool-id+" .. title
       end
    }
  }
}

Note

Although some logic is case insensitive, testing on Linux revealed that not all of it is. For this reason,
the case of template specified in the customization ("zettel" in this example") should match the name
and case of the template id

Note

This is a duplicate of #174 because the original forked repository was based on the deprecated epwalsh version, so
I had to delete that fork, and recreate it based on obsidian-nvim/obsidian.nvim

Secondary changes

Add deps/ directory to .gitignore

• They are generated automatically, so they don't need to be tracked

PR Checklist

• The PR contains a description of the changes
• I read the [CONTRIBUTING.md] file
• The CHANGELOG.md is updated
• The changes are documented in the README.md file
• The code complies with make chores (for style, lint, types, and tests)

[neo451]

ok after a while I finally get what the PR is trying to do, pretty cool stuff!!

But that is quite a sign that we need to put docs, you can put a new section in the wiki's template page, named ### customizations, and link to it in the readme's config comments.

Any chance the new_from_template_spec.lua can be rewritten in mini.test? otherwise it is just not tested for the moment.

---

The following points are not needed to be addressed and just for discussion only.

It feels a bit clunky to change the client's config and then restore it. As I discussed in https://github.com/orgs/obsidian-nvim/discussions/140#discussioncomment-13088512

Having a client that don't hold very many state is just not good for both development and user scripting.

A simple create_note function that takes all the context like template to use, name, and path, would be much nicer, and this PR could be simpler to understand with it.