85ea64211f
* ui: Discovery-Chain: Cope with redirects that have failovers We found a few stranger configurations for discovery-chain, one of which was redirects that can then failover. We altered the parsing here to include 2 passes, one to organize the nodes into resolvers and children/subsets based on the nodes themselves, which includes adding the failovers to resolvers and subsets. We then do a second pass which can more reliably figure out whether a target is a redirect or a failover (target failovers don't have a corresponding node), this then adds the redirect children to the already exising resolver (from the first pass) and then checks if the redirect also has failovers and adds those if so. * ui: Check to see if we have a user configured default route or not ...if we don't add one so the visualization looks complete |
||
|---|---|---|
| .. | ||
| adapters | ||
| components | ||
| computed | ||
| controllers | ||
| forms | ||
| helpers | ||
| initializers | ||
| instance-initializers | ||
| mixins | ||
| models | ||
| routes | ||
| routing | ||
| search/filters | ||
| serializers | ||
| services | ||
| styles | ||
| templates | ||
| utils | ||
| validations | ||
| app.js | ||
| env.js | ||
| index.html | ||
| resolver.js | ||
| router.js | ||