Find problem plugin via bisection / binary search

What is the smartest way to find out what plugin is likely buggy?

In git, I’d bisect, or do a binary search.

Are there any plugins to assist with this, or any tips on how to make the process easier?

The hardest parts for me are:

  • Remembering which parts of the search space I’ve already excluded
  • Manually flipping the switches to change the search space

What I’ve tried:

  • Commenting with // lines in .obsidian/community-plugins.json
    • The file gets seen as invalid and replaced with an empty array
  • Adding another array to the same file
    • Whole file is again zapped with an empty array

Could you allow comments in .obsidian/community-plugins.json, or a 2nd array which has disabled plugins?

For now, it seems a separate file is required to make this possible.

There is already such a plugin actually:
:crossed_swords: Divide & conquer

obsidian://show-plugin?id=obsidian-divide-and-conquer

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.