TYPO3 Core

I really like eval options uniqueInSite and uniqueInPid in the slug field. But I don't understand how the uniqueInPid option is resolved in the frontend.

In my project I have similar structure to this:

• Folder A
• Folder B
• Detail page A ... (Record storage in the Plugin tab is set to "Folder A")
• Detail page B ... (Record storage in the Plugin tab is set to "Folder B")

Suppose we have our own object type (eg. Project) and different types of projects stored in different folders. 1st type is stored in "Folder A" and displayed on "Detail page A", 2nd type use "Folder B" and "Detail page B". When I save two different projects with the same name in different folders, the same slug will be generated for them (eg. big-project), which is fine due to the uniqueInPid option.

Now, in the frontend I get two different URLs:

• /detail-page-a/big-project ... (should display project from "Folder A")
• /detail-page-b/big-project ... (should display project from "Folder B")

But in both cases the first "big-project" from table is displayed, the record storage (field [pages]) is ignored. The TYPO3\CMS\Core\Routing\Aspect\PersistedAliasMapper use language and frontend (deleted, hidden etc.) restrictions but there is no check for PID.

Is this a misconfiguration or a bug?