TYPO3 Core

Let's imagine we have a list of postings on a blog or something similar.
The postings have their own page with a slug.
We use the routeEnhancer to create nice links.
The users can create new postings in the frontend and preview them (in FE) before publication (DB data field hidden = 1).

In the list of postings we have links something like this:

https://xyz.ch/postings?tx_extension_plugin[action]=list&tx_extension_plugin[controller]=Posting&tx_extension_plugin[posting]=160&cHash=1991dd7f9cb3b962f399148a8f8ec86b

Slug of posting 160 is: 'travel-to-new-zealand'

If the page is not hidden (=0), the routeEnhancer delivers the link 'travel-to-new-zealand' as defined in the slug.
If the page is hidden (=1), the routeEnhancer respectively the aspects delivers only the output: 160.

Of course, page 160 is not found and a 404 Not Found error results.

However, it shouldn't be aspects' responsibility whether it does its job or not if the page is hidden.
Aspects should also work for hidden pages (preview pages in FE).