Make error message more informative, to try to reduce user pain and support effort.

[claremacrae]

Several people have reported tags not working, and either they weren't using the latest, or had not restarted Obsidian.

I already added an issue about noting in the docs the version number when new features were added.

I'm thinking of changing the following in code:

• Add tasks version number to error output
• Add an encouragement to restart Obsidian if you have just updated the plugin
• Add the full input line to all error messages

[claremacrae]

I had a look at including the Plugin version number in error messages in the 1.7.0 release, if it was an easy win.

It turns out that the plugin version number is not currently accessible in the TypeScript source code, it's only in the manifest.json. Adding code to read files requires more testing than the quick initial win I was after, so I'll leave this for a later release, in order to get the 1.7.0 features out to users.

An alternative would be to include the version number in the source code, and change the release process so that it updates the version number in the relevant source code every time. That may well be easier.

[claremacrae]

It is possible to obtain the version number from the manifest:
https://github.com/obsidianmd/obsidian-api/blob/902badd38ba907689f0917d7b193f7e33d1284fe/obsidian.d.ts#L2684-L2724