You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now we have a lot of plugins available it's become important for the user to manage them properly from within pry. This functionality could be provided by one command or a suite of commands, but the minimum functionality should be:
List which plugins are installed
List which plugins are active.
View a list of all available plugins on rubygems, with descriptions, and their dependencies
Possibly install new plugins
Possibly uninstall plugins
Possibly disable active plugins
Possibly enable deactivated plugins
If we want to allow enabling/disabling plugins, it is important we refactor the plugin system and provide it with a few hooks and a way of defining plugin functionality so that they can be activated/deactivated on demand.
Further, this would allow for the proper treatment of plugins like pry-nav which monkeypatch pry core methods
The text was updated successfully, but these errors were encountered:
A marked in bold entry indicates that it has been implemented:
List which plugins are installed
List which plugins are active.
View a list of all available plugins on rubygems, with descriptions, and their dependencies
Possibly install new plugins
Possibly uninstall plugins
Possibly disable active plugins
Possibly enable deactivated plugins
Currently, I'm waiting for Ryan's (@rf-) refactoring of tests to be merged with master. I haven't added any single test on my branch for this new functionality: I just don't want to resolve a ton of merge conflicts in the end.
Now we have a lot of plugins available it's become important for the user to manage them properly from within pry. This functionality could be provided by one command or a suite of commands, but the minimum functionality should be:
If we want to allow enabling/disabling plugins, it is important we refactor the plugin system and provide it with a few hooks and a way of defining plugin functionality so that they can be activated/deactivated on demand.
Further, this would allow for the proper treatment of plugins like
pry-nav
which monkeypatch pry core methodsThe text was updated successfully, but these errors were encountered: