Use case or problem
I’ve installed a couple of plug-ins recently that proved to be problematic.
When I subsequently checked the “Issues” for them on Github it appeared the bug had already been reported, but the plug-ins haven’t been updated for a while.
I have since then uninstalled the plug-ins.
Proposed solution
Consider creating a review feature or star-rating that will guide decison-making in selecting plug-ins (similar to the way plug-ins are rated in Wordpress?).
Current workaround (optional)
None, just trial and error. It gets quite annoying when a numbering feature runs riot on your document and you have to waste a lot of time repairing it.
Related feature requests (optional)
3 Likes
As a workaround: Personally, I use git as version control. So I can always commit a snapshot before installing a new plugin, and roll back if I have to.
The warnings are clear when you enable community plugins. Whether this feature was ever implemented or not, you should still A) have good backups, B) consider using version control software, C) check the project page of the plugin before installing.
–
There is also a LOT of discussion on the topic here. Security of the plugins
3 Likes
Installing new community plugins can often feel like a gamble. A ratings and reviews system is essential to quickly determine a plugin’s reliability. Furthermore, such a system would motivate plugin developers to resolve issues, improve quality, and foster healthy competition.
Given the Obsidian team’s limited resources for manual review moderation, even a simple 5-star rating system would go a long way.
Alternatively, one can check a plugin’s score on Obsidian Stats, though it lacks detailed community ratings and reviews.