Plugin initialization procedure about obsidian-git HOT 8 CLOSED

Okay, I will add that.

from obsidian-git.

Yes I thought about something similar.

from obsidian-git.

Thank you for providing such a good idea.
May I know what if I want to use your version, how am I suppose to do?
I tried copying your ts file and edit the existing manifest.json from "js:main.js" to "js:main.ts", but it fails to initialize.

from obsidian-git.

You'll want to build the .ts file to a .js version using the build pipeline - just run npm install to install dependencies then npm run build to actually build the final file.

from obsidian-git.

thank you for the suggestions!

from obsidian-git.

@lishid You are right, that some users complain about missing settings page or commands, but why should the commands be registered, when the plugin fails in initialization? Other tasks though should of course be moved to other functions.

from obsidian-git.

The command could gracefully fail with a message, keeping the plugin experience consistent. Right now the biggest friction is that if something goes wrong, the user has no idea what's going on, or how to solve it, without joining the discord and ask for tips.

from obsidian-git.

I'd suggest some way to re-run the initialization process should it fail - then everything else that depends on internal state of the initialization could re-run the initialization step when it's triggered (like showing the settings pane, triggering a command). That way, the user doesn't have to reload the app (or disable/enable the plugin) once they fix the issue.

from obsidian-git.