The Unitade plugin for Obsidian provides a versatile solution for managing file extensions within the app. It allows users to open and edit files with custom extensions, something that is not supported by default in Obsidian. The plugin enables rendering files with various extensions as code, similar to editors like VS Code, and offers compatibility modules for older plugin versions. Users can configure the plugin to handle specific file types by entering their extensions in the settings. Unitade is designed for those who want to expand Obsidian's capabilities and streamline the process of working with non-standard file types in their vault.
This patch fixes problems with two systems: applying and unapplying systems
which were updated after previous (v3.2.5) update:
[!Note]
This patch is a must-have because it fixes primary issues with using code editor and
default extensions systems at the same time: if you use grouped extensions, patch of
this won't affect your performance or working pipeline.
- previously, apply system was "one-directional", meaning when it tried to apply
one of the extensions modes, it would ignore one, which was a big oversee in the system,
for more info, see #137. - accordingly to update of applying system, unapplying system was also fixed: now it asks
for real-time value of markdown overcharge and unapplies every registry of extension in
the plugin, for more info and fix, see #139.
[!Tip]
Check commit history of this release in: v3.2.6 - release note
Or in the draft of pull request: https://github.com/Falcion/UNITADE.md/pull/138