Meeps
October 23, 2022, 7:23pm
1
I’m working on a plugin to allow users to register views to file extensions in a modular manner. I’ve found this function:
To register extensions, but I need to figure out how to de-register extensions when a user changes their settings. Is this possible using a different function or null parameter of some think? Or is it append only?
Meeps
October 24, 2022, 4:24pm
2
I found t by decompiling the api myself. and have made a plugins with an example here:
obsidianmd:master ← MeepTech:patch-1
opened 04:02AM - 24 Oct 22 UTC
# I am submitting a new Community Plugin
## Repo URL
Link to my plugin: https:… //github.com/MeepTech/obsidian-custom-file-extensions-plugin
## Release Checklist
* [x] I have tested the plugin on
* [x] Windows
* [x] macOS
* [x] Linux
* [ ] Android _(if applicable)_
* [ ] iOS _(if applicable)_
* [x] My GitHub release contains all required files
* [x] `main.js`
* [x] `manifest.json`
* [ ] `styles.css` _(optional)_
* [x] GitHub release name matches the exact version number specified in my manifest.json (_**Note:** Use the exact version number, don't include a prefix `v`_)
* [x] The `id` in my `manifest.json` matches the `id` in the `community-plugins.json` file.
* [x] My README.md describes the plugin's purpose and provides clear usage instructions.
* [x] I have read the tips in https://github.com/obsidianmd/obsidian-releases/blob/master/plugin-review.md and have self-reviewed my plugin to avoid these common pitfalls.
* [x] I have added a license in the LICENSE file.
* [x] My project respects and is compatible with the original license of any code from other plugins that I'm using. I have given proper attribution to these other projects in my `README.md`.