Skip to content

Reorganise Error Messages

Problem

Currently, error messages are defined either at the line where the error is thrown, or at the beginning of the class as static string. This clutters code. In addition, dynamic content can only be appended causing "unnatural" or ambiguous error messages.

Requirements

  • Error messages shall be referencable in unit tests (i.e. statically defined)
  • Placeholder should allow to enhance error messages with dynamic content
  • Error messages shall be defined not in the classes throwing them - to reduce code to its actual function.

Suggestion

see

Edited by Christoph Schimeczek
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information