If plugin is installed but can't be loaded, user shouldn't be prompted to install the plugin again

chronicle-app / chronicle-etl

📜 A CLI toolkit for extracting and working with your digital history

https://chronicle.app/

MIT License

149 stars 3 forks source link

If plugin is installed but can't be loaded, user shouldn't be prompted to install the plugin again #34

Closed hyfen closed 2 years ago

hyfen commented 2 years ago

In PluginRegistry#activate, we can add gem 'chronicle-NAME' and watch for a Gem::MissingSpecError (or maybe via an #installed? method)

Currently, we're only doing require 'chronicle/NAME' which generates a LoadError if the gem is missing OR if the gem fails while loading. This seems to be the problem in #33.