Almost 1/3 of plugins’ code is always the same. Writing it all over again makes process error-prone and time-consuming. So, we collected the best parts of the plugins and put them together to solve the problem. What common parts did we find? Every plugin uses a logger, so we implemented the PSR-3 logger with configurable parameters. A Configuration Manager with environment detection. The API Wrapper – a collection of methods and arguments easily callable with standard method chaining technique.
Filesystem API, Storage, Dependency Container, HTTP client – to make SDK and plugins testable. Implementing all features with one day is impossible, so we started adding functions while developing plugins. One day we cover the reasonable amount of the API and developers can develop plugins without looking the API documentation.
Every plugin must:
Why it is so important?
What plugin development looks like?
/bin – executable scripts
/config – configuration files
/tmp – temporary files
/library – plugin classes
/public – publicly available files
/tests – test files
Contact our support to get started with the Erply Plugin SDK.