Enable buttons to insert Obsidian native templates

[jshumway]

Please fill out these Check-boxes

• I checked for existing similar feature requests
• I have read the docs and checked that the feature I am requesting is not already implemented
• My feature request consists of only one feature

Is your Feature Request related to a Problem or Annoyance?

No.

Describe the Feature you'd like

Buttons should be able to insert an Obsidian native template (I.e., the core plugin “templates”) with just a button press.

One option would be to add a new action for built in templates.

Presently, the options are to:

• setup and learn Templater
• setup a button to run the “Insert template” command, followed by an input action to enter the name of the template, then manually click on the highlighted template name
• use and insert text action and put the body of the template into the buttons definition; template variables like {{title}} don’t work.

Alternatives

It would also be possible to enable this behavior by allowing the input action to accept the template from the list brought up by the “insert template” option, instead of the user clicking or hitting “done” (on mobile).

Additional Context

If there is an implementation plan that isn’t too complicated I’d be happy to take a stab at it, of this is a feature that is acceptable for this plugins design.

[jshumway]

I started digging through the source code to try and prototype this, but pretty quickly ran into the architecture mismatch; namely that the AbstractButtonActionConfig experts run to return the contents of the note post-insert as a big string, whereas shabegom/buttons invokes insertTemplate on the core templates plugin, which mutates the note. It also requires a handle to the overall Obsidian app, which isn't readily available in the content of an AbstractButtonActionConfig.

Maybe there is a nice way to work around those roadblocks, but I'll just breakdown and finally install Templater.

[mProjectsCode]

I am not sure where you got the idea about returning the note contents, as AbstractButtonActionConfig#run returns Promise<void>.

The second point about app access is true, but for good reason, as the meta bind core is independent of the Obsidian API. The InternalAPI class serves as an adapter to the Obsidian API; see the ObsInternalAPI class.

[jshumway]

I am not sure where you got the idea about returning the note contents, as AbstractButtonActionConfig#run returns Promise.

Ah I see, I was read InsertIntoNoteButtonActionConfig.ts and was looking at the callback's return, which is actually for atomicModify, not the run callback.