Currently, there is insufficient validation that a user-defined assessment hook takes the correct number of arguments (arity) or that it returns the expected type.
This can lead to a difficult-to-recover situation, especially if it has to do with a hook like listOptions which is called every time the user views an assessment's landing page. (they would have to navigate directly to the edit page to reload the config file)
Currently, there is insufficient validation that a user-defined assessment hook takes the correct number of arguments (arity) or that it returns the expected type.
This can lead to a difficult-to-recover situation, especially if it has to do with a hook like
listOptionswhich is called every time the user views an assessment's landing page. (they would have to navigate directly to the edit page to reload the config file)