2.1 Path.toDisplayPath() bug or feature?? :)

[nyronian]

Am I crazy or has something changed in toDisplayPath() within the Path class between 2.0 and 2.1.  Below is my example/issue:

I have a noderef with the following path:

spaceA->spaceB->spaceC‍

in 2.0 toDisplayPath() on noderef for spaceC would return:

spaceA/spaceB/spaceC‍

in 2.1 it is not including the name of the current noderef, it returns:

spaceA/spaceB‍

To get the full display path in 2.1, I have changed all my code with the upgrade to call

toDisplayPath()+"/"+Name_of_current_node‍

Just want to verify if this was a bug or intentional.  I have done quite a bit of testing around this trying to verify the issue, you should easilly be able to duplicate it.

[derek]

Hi,
It's not intentional, so it's probably a bug.
What do the different toString() methods reveal?  In other words, it it the code that constructed the Path object that is at fault or the code that generates the name path.