Add option to evaluate dataview codeblocks

[j-mcavoy]

Hi there 👋,

I am a big fan of this plugin and it greatly increases what I can do within Obsidian! I have an idea to make this plugin even better for me and hopefully for many others that use it!

Feature description

I would like a way for a user to optionally have their dataview code blocks evaluated (i.e. evaluate the markdown that the dataview code block generates on the fly and write it to the actual file).

This feature would be great since it can leverage dataview's ability to dynamically generate markdown text with all the benefits of plaintext markdown files and how Obsidian does it's searching, tagging, linking, etc. between these files.

Currently, Obsidian doesn't see the tags, file links, etc. generated by dataview code blocks, it just sees a block of text.

Practical use case

For instance, I use dataview scripts in my daily entry template to pull meta-info about files such as which files I created / modified, tasks I completed that day, etc. and generate lists with links to these files. The content created by these dataviews will change throughout the day, but then it will be static forever after. So it would be nice to have an easy way to save this generated text to the actual markdown file.

Implementation idea

1. The user writes adds dataview code to their markdown file...
   # Example
   ```dataview
   list where file.ctime = date(today)
   ```
2. They can see the output in read mode:

# Example
 - [[File 1]]
 - [[File 2]]

4. They hover over the dataview output, next to the </> Edit this Block icon, there
   
   is a ▶️ icon to evaluate the expression and write it to the file.

They click it. And the file contents changes to:

# Example
 - [[File 1]]
 - [[File 2]]

and the dataview code block either

1. is deleted entirely, leaving only the output
2. is just commented out with % to hide it so the user could revert this change. Something like:

# Example
% \`\`\`dataview
% list where file.ctime = date(today)
% \`\`\`
 - [[File 1]]
 - [[File 2]]

[j-mcavoy]

Created issue #941

[blacksmithgu]

See #42 which should include your specific use case.