{"push_id":1302984122,"size":1,"distinct_size":1,"ref":"refs/heads/force-route-state-change","head":"922cba83f54f73a39afc19956433d5173afc06f5","before":"5eb75e8534b44a8e1458d0d94cf02835bac848fd","commits":[{"sha":"922cba83f54f73a39afc19956433d5173afc06f5","author":{"name":"Chris Joel","email":"c3dade29e763c289f1d1a186403f47d945417d9f@google.com"},"message":"Reset `tail` as routes deactivate.\n\nThis change proposes that `tail` should be reset when a route\ndeactivates. This has two important side-effects that need to be\nconsidered:\n\n 1. Child routes that no longer match the current path will become\n \"inactive\". Note that this is already true today in some circumstances,\n but not others, so the change brings consistency across all types of\n route path changes.\n 2. The `tail` values down a routing branch will blink on and off in\n ways that they did not before. This is important to consider for\n performance purposes.\n\nRegarding #2, the justification for this change is that `data` will\nstill remain consistent despite any thrashing of the `tail`, so UI\nstate can rely on `data` to avoid thrashing.","distinct":true,"url":"https://api.github.com/repos/PolymerElements/app-route/commits/922cba83f54f73a39afc19956433d5173afc06f5"}]}
{"actor":{"display_login":"cdata"}}