The plugin development guide suggests cloning your plugin repository into /.obsidian/plugins directly. An alternative approach to storing your project in the. cd into this directory and run yarn and yarn build (or npm i and npm run build). Checkout local workspaceĬlone or create your plugin project workspace. Now we’re ready to test our plugin in the desktop environment. Connect to the vault and click Start Synching.Go to Sync settings > Pick remote vault and click the Choose button.Go to Settings and enable the Sync plugin.In order to propagate changes to your plugin to other devices, you will need to use a synchronization method. This is also a good time to change any other settings you need to adjust and to install other plugins you need. Open the test vault in Obsidian and go to Settings > Community plugins and disable safe mode to allow third party plugins. On a desktop system (Mac, Linux or Windows), create a new vault for testing your plugin, e.g. Plugins can modify and delete notes, folders and even the entire vault, so always work in a test vault. It’s important not to do plugin development and testing in your regular notes vault. I use Obsidian Sync, but other methods will also work. Setup your environmentįor testing on multiple platforms, you’ll need some sort of synchronization method available. And it isn’t uncommon to discover issues that are unique to mobile or a specific platform. While most plugins that work on desktop will probably work OK in other environments, there’s no way of knowing for sure without testing first. When developing a plugin for Obsidian, it is important to make sure it behaves correctly on all of the platform types that it is going to run on. This guide assumes you are familiar with the basics. If you’re new to Obsidian plugin development, check out the Obsidian Plugin Developer Docs. Testing and debugging an Obsidian plugin on multiple platforms.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |