Splat routes with final fixed route segments
I have a use case that right now it's not supported by TSR. I work with a CMS that uses a concept that is called "object traversal" to retrieve the objects stored in the CMS database.
The objects are stored in an objects/documents DB that is able to store them in a hierarchically way (as a file system, with parent/child structure). So they map the way it's stored directly with the natural organization of a website:
in the DB, the
so when the user calls that URL, it traverses the tree until it gets to the
We can match this via "splat" routes, all fine.
Then, the tricky part. The traversal concept also accepts the idea of "views" or actions applied to the content objects. Then the edit view becomes:
I noticed this can't be achieved, nor in TSR, nor in any other modern router. We are using RR5, which supported this back then, but I noticed that RR6 does not support it either.
Is that something that it's sensible to add as a feature? is it difficult to achieve?
Thanks for in advance!
The objects are stored in an objects/documents DB that is able to store them in a hierarchically way (as a file system, with parent/child structure). So they map the way it's stored directly with the natural organization of a website:
/folder/nested-folder/pagein the DB, the
foldernested-folderpageso when the user calls that URL, it traverses the tree until it gets to the
pageWe can match this via "splat" routes, all fine.
Then, the tricky part. The traversal concept also accepts the idea of "views" or actions applied to the content objects. Then the edit view becomes:
/folder/nested-folder/page/editI noticed this can't be achieved, nor in TSR, nor in any other modern router. We are using RR5, which supported this back then, but I noticed that RR6 does not support it either.
Is that something that it's sensible to add as a feature? is it difficult to achieve?
Thanks for in advance!
