Go to file
Lars b99416b67d
Some checks failed
Node.js build / build (20.x) (push) Has been cancelled
Node.js build / build (22.x) (push) Has been cancelled
Implement WP-26 features for Section-Types, Block-IDs, and Edge Suggestions
- Enhanced the interview configuration parsing to support section_type, block_id, and generate_block_id properties.
- Updated the renderer to incorporate Section-Types and Block-IDs, allowing for automatic edge suggestions during markdown rendering.
- Introduced new RenderOptions for improved handling of graph schema and vocabulary in the rendering process.
- Implemented tracking of Section-Info during the wizard flow, including updates for loop items and nested steps.
- Enhanced the InterviewWizardModal to support Block-ID selection for intra-note links, improving user experience and functionality.
2026-01-27 11:18:56 +01:00
.github/workflows update sample plugin with eslint instructions 2025-11-10 12:26:07 +01:00
Dictionary Refactor analysis policies and update chain roles and templates 2026-01-21 07:17:29 +01:00
docs Update documentation index to include WP-26 integration details 2026-01-26 18:53:28 +01:00
scripts Refactor plugin to Mindnet Causal Assistant with enhanced vocabulary management and linting features. Updated manifest and package files to reflect new plugin details and dependencies. Added commands for reloading vocabulary and validating notes. 2026-01-15 11:34:29 +01:00
src Implement WP-26 features for Section-Types, Block-IDs, and Edge Suggestions 2026-01-27 11:18:56 +01:00
tests/fixtures Enhance template matching and chain inspection features 2026-01-18 22:10:44 +01:00
.editorconfig use LF instead of CRLF (#28) 2022-04-15 14:13:31 -04:00
.gitignore Update .gitignore (#25) 2022-01-28 10:34:53 -05:00
.npmrc add version bump script (#10) 2022-01-22 16:13:50 -05:00
AGENTS.md language 2025-09-05 09:10:47 -07:00
esbuild.config.mjs update eslint plugin version 2025-11-14 14:28:33 +01:00
eslint.config.mts update sample plugin with eslint instructions 2025-11-10 12:26:07 +01:00
experience_cluster_config.yaml Eingebette Loops 2026-01-16 20:10:08 +01:00
LICENSE Add license, fixes #98 2025-01-27 21:38:01 +00:00
manifest.json Refactor plugin to Mindnet Causal Assistant with enhanced vocabulary management and linting features. Updated manifest and package files to reflect new plugin details and dependencies. Added commands for reloading vocabulary and validating notes. 2026-01-15 11:34:29 +01:00
package-lock.json Enhance interview functionality and settings; add YAML dependency 2026-01-16 12:27:44 +01:00
package.json Enhance interview functionality and settings; add YAML dependency 2026-01-16 12:27:44 +01:00
README.md Fix typo in ESLint plugin link 2025-12-30 13:09:48 -05:00
styles.css Implement Interview Wizard Modal enhancements with new CSS styles and markdown support 2026-01-16 14:11:04 +01:00
tsconfig.json update eslint plugin version 2025-11-14 14:28:33 +01:00
version-bump.mjs build: only write new minAppVersion requirements to versions.json 2025-04-28 08:38:38 +02:00
versions.json Update for 0.15 2022-08-09 13:38:50 -04:00
vitest.config.ts Refactor plugin to Mindnet Causal Assistant with enhanced vocabulary management and linting features. Updated manifest and package files to reflect new plugin details and dependencies. Added commands for reloading vocabulary and validating notes. 2026-01-15 11:34:29 +01:00

Obsidian Sample Plugin

This is a sample plugin for Obsidian (https://obsidian.md).

This project uses TypeScript to provide type checking and documentation. The repo depends on the latest plugin API (obsidian.d.ts) in TypeScript Definition format, which contains TSDoc comments describing what it does.

This sample plugin demonstrates some of the basic functionality the plugin API can do.

  • Adds a ribbon icon, which shows a Notice when clicked.
  • Adds a command "Open modal (simple)" which opens a Modal.
  • Adds a plugin setting tab to the settings page.
  • Registers a global click event and output 'click' to the console.
  • Registers a global interval which logs 'setInterval' to the console.

First time developing plugins?

Quick starting guide for new plugin devs:

  • Check if someone already developed a plugin for what you want! There might be an existing plugin similar enough that you can partner up with.
  • Make a copy of this repo as a template with the "Use this template" button (login to GitHub if you don't see it).
  • Clone your repo to a local development folder. For convenience, you can place this folder in your .obsidian/plugins/your-plugin-name folder.
  • Install NodeJS, then run npm i in the command line under your repo folder.
  • Run npm run dev to compile your plugin from main.ts to main.js.
  • Make changes to main.ts (or create new .ts files). Those changes should be automatically compiled into main.js.
  • Reload Obsidian to load the new version of your plugin.
  • Enable plugin in settings window.
  • For updates to the Obsidian API run npm update in the command line under your repo folder.

Releasing new releases

  • Update your manifest.json with your new version number, such as 1.0.1, and the minimum Obsidian version required for your latest release.
  • Update your versions.json file with "new-plugin-version": "minimum-obsidian-version" so older versions of Obsidian can download an older version of your plugin that's compatible.
  • Create new GitHub release using your new version number as the "Tag version". Use the exact version number, don't include a prefix v. See here for an example: https://github.com/obsidianmd/obsidian-sample-plugin/releases
  • Upload the files manifest.json, main.js, styles.css as binary attachments. Note: The manifest.json file must be in two places, first the root path of your repository and also in the release.
  • Publish the release.

You can simplify the version bump process by running npm version patch, npm version minor or npm version major after updating minAppVersion manually in manifest.json. The command will bump version in manifest.json and package.json, and add the entry for the new version to versions.json

Adding your plugin to the community plugin list

How to use

  • Clone this repo.
  • Make sure your NodeJS is at least v16 (node --version).
  • npm i or yarn to install dependencies.
  • npm run dev to start compilation in watch mode.

Manually installing the plugin

  • Copy over main.js, styles.css, manifest.json to your vault VaultFolder/.obsidian/plugins/your-plugin-id/.

Improve code quality with eslint

  • ESLint is a tool that analyzes your code to quickly find problems. You can run ESLint against your plugin to find common bugs and ways to improve your code.
  • This project already has eslint preconfigured, you can invoke a check by runningnpm run lint
  • Together with a custom eslint plugin for Obsidan specific code guidelines.
  • A GitHub action is preconfigured to automatically lint every commit on all branches.

Funding URL

You can include funding URLs where people who use your plugin can financially support it.

The simple way is to set the fundingUrl field to your link in your manifest.json file:

{
    "fundingUrl": "https://buymeacoffee.com"
}

If you have multiple URLs, you can also do:

{
    "fundingUrl": {
        "Buy Me a Coffee": "https://buymeacoffee.com",
        "GitHub Sponsor": "https://github.com/sponsors",
        "Patreon": "https://www.patreon.com/"
    }
}

API Documentation

See https://docs.obsidian.md