Best practice for plugin dependencies

Support Plugins
1

I’ve written several plugins for shortcodes. All of them obviously depend on shortcode-core.

However, when testing code I try to install the minimum number of plugins, and I forget to install shortcode-code.

What is the best practice for ensuring that a plugin which depends on another plugin installs the dependency first?

I have searched using ‘grav dependencies’ and come across references to the file .dependencies but there does not seem to be any easily available description about what .dependencies should contain.

In addition, there is a post saying that .dependencies is a hold-over from a previous development system, and that indicates it is not the best way forward.

2

In my opinion, always use the dependencies in the plugin’s blueprints, and use them exhaustively.

This will ensure that GPM installs the dependencies only if they resolve with the current Grav-environment.

3

I looked up google-maps, a plugin I’ve used that I know depends shortcode core, and saw that it uses the plugin blueprint as per Ole’s comment.

4

Thanks everyone.

I missed the reference in Plugin Blueprints.