Inspecting and debugging routes is now easier than ever.

We have added the Route Inspector page in our app, enabling you to see what's going on quickly.

What do we mean by that? You see, routes can be a little tricky to debug, to put it mildly.

Let's first look at a "normal route" - a generated view.

Here we can see that the route /fairy-tales/the-snow-queen/ is generated by the source entity 1147-en-us, which gives us the view 1147-en-us/View/contentPage.

That's great and precisely the expected behaviour for most routes. What can be confusing and introduce head-scratching is when we start having redirects. 

Say we have a redirect for the route /fairy-tales/the-fire-king/, which is generated by source entity 1234-en-us, take redirects us to /fairy-tales/the-snow-queen/.

Before the route inspector, finding exactly which source entity was causing this redirect could be tedious. Now it is much easier to get a feel of what's going on.

As we can see in the example above, we can quickly locate which source entity is causing the redirect.