Talk:Errors handling in web services: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
Jerome Mouneyrac - 08/05/2012 | Jerome Mouneyrac - 08/05/2012 | ||
About the exception format (https://docs.moodle.org/dev/Errors_handling_in_web_services#How_to_handle_exception_on_the_client_side): | |||
* I wonder if 'message' should be translated | * I wonder if 'message' should be translated or not | ||
* I wonder if 'debuginfo' could have a defined structure like: code_error_string | english_human_message | some_ids_or_json_code_in_order_to_help_client_dev | * I wonder if 'debuginfo' could have a defined structure like: code_error_string | english_human_message | some_ids_or_json_code_in_order_to_help_client_dev | ||
* | * sometimes exceptions are thrown at lower level so except if we try-catch the entire external function we can't change them. | ||
* we can not change much of the existing web service exception without potentially breaking existing clients. |
Revision as of 03:19, 8 May 2012
Jerome Mouneyrac - 08/05/2012
About the exception format (https://docs.moodle.org/dev/Errors_handling_in_web_services#How_to_handle_exception_on_the_client_side):
- I wonder if 'message' should be translated or not
- I wonder if 'debuginfo' could have a defined structure like: code_error_string | english_human_message | some_ids_or_json_code_in_order_to_help_client_dev
- sometimes exceptions are thrown at lower level so except if we try-catch the entire external function we can't change them.
- we can not change much of the existing web service exception without potentially breaking existing clients.