|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I guess from a programmatic point of view a node name of null is ok, but what about the string representation? I think a human readable version of the path is still important (standardized or not). For example see MethodLevelValidationTest#cascadingArrayReturnValue. The string version of the path is "cascadingArrayReturnValue.$retval[1].name". How would this look like with a null node name. I guess toString of PathImpl could somehow still insert a name like 'retval', but that seems inconsistent.