[
https://issues.apache.org/jira/browse/DAFFODIL-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004253#comment-18004253
]
Olabusayo Kilo commented on DAFFODIL-2999:
------------------------------------------
A note from Steve from this PR:
https://github.com/apache/daffodil/pull/1479#discussion_r2183116929
I think {{getMessage()}} wants to just call {{toString()}} so that it returns
the context, mode, etc. so that it matches the current API.
There is a bug to change this behavior so that it returns what you currently
have and we remove getMessageOnly, but that can be done in a separate PR.
Though, there is a chance changing this to toString will break things. If it
does, then we can keep this change as is, as long as we plan to change the
behavior and drop getMessageOnly()
> Remove Diagnostic.getMessageOnly, move behavior to getMessage
> -------------------------------------------------------------
>
> Key: DAFFODIL-2999
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2999
> Project: Daffodil
> Issue Type: Task
> Components: API
> Reporter: Steve Lawrence
> Priority: Major
> Fix For: 4.0.0
>
>
> DAFFODIL-2984 added a getMessageOnly function to get just the message instead
> of the message + mode + schema location + data location.
> Really, getMessage wants to provide this functionality, but the new function
> was added to ensure backwards compatiblity. Daffodil 4.0.0 will break
> compatiblity with a number of APIs, so as part of 4.0.0 we should remove
> getMessageOnly and change getMessage so it returns just the message. We'll
> need to make sure to document this part of the migration guide.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
