Developing plugins right

5 sept. 2025 1 min read 1 views

Clear structure

Separate responsibilities consistently. Controllers receive requests, services hold the logic and repositories take care of data. This separation makes your code testable.

Rely on proven tools

Use the tools the system already provides instead of reinventing the wheel.

Dependency injection for loose coupling
Events instead of hard wiring
Migrations for every database change

Externalise configuration

Values that may change belong in the configuration and not hard coded. That keeps your plugin flexible.

Test and safeguard

Automated tests give you confidence during updates. Even a few well chosen tests prevent old bugs from returning.

Think about updates

Write your code so it still works after the next system update. Avoid internal interfaces that can change at any time.

Conclusion

Clean architecture is not an end in itself. It saves you many hours later and makes your plugin understandable for others.