Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History
* Currently, developers must rely on exception messages to understand why and/or where an exception was thrown. This has led to several requests for translatable exceptions and/or development of unique exception codes -- all of which lead to increased maintenance costs.

To illustrate, with the current situation, if we want to handle different exceptions from the same component separately, we need to know (a) what type of exception is thrown, and (b) some static part of the exception message:
exceptions from the same component separately, we need to know (a) what type of
exception is thrown, and (b) some static part of the exception message:

{code:php}