We know that one of the biggest challenges during plug-in development is matching COYO's user interface design and user experience. To fully create the illusion that a plugin is part of COYO, it must completely blend in.
A new version of the plugin-adapter has just been published via https://www.npmjs.com.
A new version of the plugin-adapter has just been published via https://www.npmjs.com. It fixes incorrect plugin certificates embedded in the adapter to validate the JWT communication with COYO environments.
COYO's plug-in integration is still labeled Beta and thus a lot of changes are happening from one version to another. But of cause we are developers ourselves and we know that constant changes and adaptions can be cumbersome and annoying. With the move to v32.x we hope to stabilize out implementation and make your life easier in the future. To help you move from your current implementation to a new v32.x compatible implementation you can use the following upgrade guide.
COYO v31.x will support the new version of the COYO lifecycle API. This makes three additional endpoints available:
instance_remove. Take a closer look at the API docs or the corresponding guides to find out more.
The first version of the new plugin-adapter is now available on npm and will be usable with v32.x of COYO. It massively simplifies the way to initialize your plug-in and to establish a working and secure connection to our COYO front-end. Just drop it into your project via npm or yarn and follow the new guidelines on how to work with the adapter. We hope you like it!
We are very excited to introduce the new COYO Developer Hub. On our way to constantly improve the documentation of and communication about COYO's plug-in API we noticed a range of missing features in our old documentation. With our move to the new platform we hope to resolve these problems.