Peter Burns

@arthurevans You could definitely extend the route matching logic to support that use case.

Can you give a demo of this failure with nested app-routes and iron-pages @chrismbeckett? Here's a jsbin to start: https://jsbin.com/hirore/edit?html,output The issue with them stomping all over each other shouldn't...

One gambit that @justinfagnani came up with, which I'll call `SPA-404` is to configure your service worker to default to serving your SPA's `index.html` file if it doesn't know what...

Another gambit is to do a very small amount of duplication, and define the outlines of the URL space for the service worker. For example, if the url space looks...

A few disorganized thoughts: - `route` is both a verb and a noun, leading to confusing sentences like `Routing is handled by passing the carbon-location's route property to the carbon-route.`...

Interestingly, I haven't heard any feedback to this effect so far. Anyone reading this who does find the repetition of `carbon-route` and the `route` property confusing, let us know with...

Given the way that `document.title` integrates with history, something keep the title up to date makes sense to me. It may make sense to put this all the way up...

IMO we do want the matching syntax to be reasonably flexible by 1.0, especially if it's a common problem (like this is), and the next best alternative isn't great (which...

This is intentional, as a gambit to reduce invisible dom changes on navigation. Quoting my response from the thread Tim links: Consider the scenario where we've got three pages: `/user`...

It is a bit surprising, but it does give an almost-free performance win. If it does cause a lot of problems for people in practice though we can revisit the...