Moodle issues submitted for review and inclusion into core are examined by our continuous integration (ci) system and checked against various automated tests. We use the automated checks to help improve the code quality in Moodle.
This page forms part of the Moodle security guidelines.
This page forms part of the Moodle security guidelines.
The Moodle Coding Style guidelines
This page forms part of the Moodle security guidelines.
The Moodle Coding Style guidelines
The Component Library is a developer tool provided to help identify frequently-used user interface components, and encourage their re-use.
This page forms part of the Moodle security guidelines.
This page forms part of the Moodle security guidelines.
This page forms part of the Moodle security guidelines.
This page forms part of the Moodle security guidelines.
This page forms part of the Moodle security guidelines.
This page forms part of the Moodle security guidelines.
This page forms part of the Moodle security guidelines.
The Moodle App Coding Style guidelines
This is the top-level page describing Moodle's coding standards and guidelines. It's the place to start if you want to know how to write code for Moodle.
This page describes how to write secure Moodle code that is not vulnerable to anything that evil people may try to throw at it.
This page forms part of the Moodle security guidelines.
This page forms part of the Moodle security guidelines.
This page describes recommended coding style for complex database queries.
This page forms part of the Moodle security guidelines.
We are looking to implement both a coding style guide, and a writing style guide, for this documentation. This will include appropriate tooling and information.
This page forms part of the Moodle security guidelines.
This page forms part of the Moodle security guidelines.