ErrorType too hard restrictions

de4a-eu / xml-schemas

DE4A WP5 authoritative XML Schemas

Creative Commons Attribution 4.0 International

1 stars 1 forks source link

ErrorType too hard restrictions #19

Closed andreasjberg closed 3 years ago

andreasjberg commented 3 years ago

The CodeErrorType has a max length of 10. This will create heavy restrictions when defining the error codes for the connector. As an example, this effectively rules out the use of prefixes such as "de4a-" in our project-defined error-codes.
The TextErrorType has a max length of 4000. This will make it impossible to display stack traces or other similarly verbose error messages crucial for effective debugging during development.

danieldecastrop commented 3 years ago

Hi!!

10 alphanumeric characters are enough to define an error code.

It is not recommended to return a stacktrace or a huge message in the response, for development you could use the logs to debug it.

Error messages should be as user friendly as possible in return message.

This has already been discussed in a call

Regards

phax commented 3 years ago

@danieldecastrop the problem here is, that we have a highly distributed system. We cannot assume, that everyone is fully "under control" of each and every logfile, so passing on information that help the other side (sender or receiver) maybe helpful (seen this in other large scale systems)

danieldecastrop commented 3 years ago

Hi @phax I have discussed it with javier Feerrero and he agrees to leave it like this, he does not apply a stacktrace or similar in the response its should be user friendly message.

Regards

phax commented 3 years ago

acknowledged