Task #440
Resolve discrepancy between Types.ErrorMessage and serialized forms
Start date:
2013-01-02
Due date:
% Done:
100%
Milestone:
Product Version:
*
Story Points:
Sprint:
Description
The definition of Types.ErrorMessage includes the following fields, both in the Types module and in the document describing exceptions:
code, detailCode, description, traceInformation
However, in the serialized forms of the exceptions in Exceptions.txt, the description field contains a nested 'message' field and an additional field called 'hint'. Need to determine which is correct.
Personally, I think the 'hint' can go in the trace information and be eliminated from the serialized form in favor of the simpler 'description' field. If we decide to keep hint, we need to guide implementors as to what kind of information should go in the hint field, as it is unspecified now.
History
#2 Updated by Dave Vieglais almost 12 years ago
- Category changed from Documentation to mn.Dryad
- Start date set to 2013-01-02
- translation missing: en.field_remaining_hours set to 0.0
