PluginConflictSeverity

How badly two plugins running side by side goes wrong, and therefore what this one does about it.

Import:

import type { PluginConflictSeverity } from 'obsidian-dev-utils/obsidian/components/plugin-gate-component';

Signature:

export enum PluginConflictSeverity

Members:

Member	Value	Description
Block	'block'	The host refuses to run at all while the conflict holds: onloadImpl never runs, nothing is registered, and the plugin explains itself the way a missing dependency does. For an overlap where both plugins acting on the same operation damages the vault.
Warn	'warn'	The host runs anyway and says the overlap is there. For an overlap that is annoying rather than destructive — duplicate commands, work done twice — where refusing to load would cost the user more than the overlap does.

---

Links to this page:

• PluginConflict