Let me begin with saying that I’m aware that this experiment might seem rather strange, but I’d very much like to understand the Aurelia child routing possibilites better and understanding the issue I’m about to present would help with that.
Have a look at this gist; https://gist.github.com/deap82/57677ba21248598d5b784dfb5940643c
Load it up in https://gist.run and open the iframe in a separate tab to see what’s going on in the address field.
The app.js defines some routes, the last one has a very generic route that only consists of parameters, which is what I would want to use, and the reason for this experiment.
The gist has three pages, don’t worry about their names, it’s just an example. You can also ignore the yellow part at the bottom.
The “Products” page has a child-router making it possible to view both the Welcome page and Contact page rendered within the child router-view. The router config is sort of the same as in app.js to enable this kind of nesting.
So I can access the Welcome page both at
#/Welcome
and
#/Products/Welcome
But on the second url I actually end up at
#/Products/Welcome/Welcome/Welcome
QUESTION 1: Why does Welcome become tripled in the hash?
If I try to go to
#/Products/Contact
I arrive at
#/Products/Contact/Welcome/Welcome
“Contact” could be anything in this example, but I would expect the Contact page rendered in the child router, due to that pages generic route pattern. Instead the Welcome page is shown within the child router…
I have to request
#/Products/Foo/Bar/Baz
to get the contact page rendered within the Products child router, the last three segments (Foo/Bar/Baz) can be anything with the exception that the last part can’t be “Welcome”.
QUESTION 2
Is there any way I could make
#/Products/Welcome
show the same thing as
#/Products/Welcome/Welcome/Welcome
and at the same time access the Welcome page as is at
#/Welcome
?
