test_configuration to detect any config level problems e.g. missing keys, missing config, etc...
1,2,3 are basically the same code, just calling a different method, so these share a check API class. 3. is only enabled if range requests are enabled.
4 is special since it runs only if the $CFG->alternative_file_system is set, whereas 1,2,3 only run if the configuration is OK (i.e. 4 is passing)
Note this only targets MOODLE_310_STABLE since lower versions (< 3.9) do not have the check API.
TODO
[ ] Improve consistency in return value of test_* functions - return check results.
A work in progress update to add some basic checks to objectfs - related to #480
Basically the idea is to expose the current methods we have available in
object_clientvia the check api https://moodledev.io/docs/apis/subsystems/checktest_permissionstest_connectiontest_range_requestAs well as add a new method:
test_configurationto detect any config level problems e.g. missing keys, missing config, etc...1,2,3 are basically the same code, just calling a different method, so these share a check API class. 3. is only enabled if range requests are enabled.
4 is special since it runs only if the
$CFG->alternative_file_systemis set, whereas 1,2,3 only run if the configuration is OK (i.e. 4 is passing)Note this only targets
MOODLE_310_STABLEsince lower versions (< 3.9) do not have the check API.TODO
test_*functions - return check results.test_*methods to try to avoid any regressions with the function signature change.get_client_checksand make them all use the check API