Write a `wp plugin gutenberg-compat` command

[danielbachhuber]

Once we have a sufficiently large dataset, it'd be helpful to have a wp plugin gutenberg-compat WP-CLI command that spits out a report of plugin compatibility for a given WP install.

Hosts can then run the command against customer WP installs, and proactively engage when they find incompatibility.

[bobbingwide]

Can you start fleshing out an API for this idea? Proposed flow

Wp site check | requests information for all active plugins and theme Wp site check all | requests information for all installed plugins and themes

Response for each plugin / theme would be:

• compatibility
• min version required

The command would then report its opinion.

Wp plugin check | Wp plugin check details | Wp theme check | Wp theme check details |

This level of request asks for more details for a specific plugin/theme.

Wp plugin inform | sends compatibility information to the server

The server should cater for unknown plugins and themes.

Wp site inform | I see a need to be able to pull the information from your server for ea

[bobbingwide]

Today I started writing some code that would consider the "Gutenberg compatibility" of the active plugins in a site. I downloaded the Extract in CSV format to opinions/plugincompatibility.csv and parsed it into an array, keyed by plugin slug.

There were 5001 lines in the original file but only 4998 records in the array. It turns out you have three duplicates in your top 5000: easy2map, portfolio, cloudinary-image-management-and-manipulation-in-the-cloud-cdn

So... now I understand that little problem, I can continue writing my code. See https://github.com/bobbingwide/oik-block/issues/20#issuecomment-380004139

Note: What I'm trying to develop in my plugin could become a small part of the solution for https://github.com/WordPress/gutenberg/issues/4981