{"action":"created","issue":{"url":"https://api.github.com/repos/neuland/micro-frontends/issues/21","repository_url":"https://api.github.com/repos/neuland/micro-frontends","labels_url":"https://api.github.com/repos/neuland/micro-frontends/issues/21/labels{/name}","comments_url":"https://api.github.com/repos/neuland/micro-frontends/issues/21/comments","events_url":"https://api.github.com/repos/neuland/micro-frontends/issues/21/events","html_url":"https://github.com/neuland/micro-frontends/issues/21","id":384901057,"node_id":"MDU6SXNzdWUzODQ5MDEwNTc=","number":21,"title":"Top-level routing","user":{"login":"andrixb","id":3845539,"node_id":"MDQ6VXNlcjM4NDU1Mzk=","avatar_url":"https://avatars2.githubusercontent.com/u/3845539?v=4","gravatar_id":"","url":"https://api.github.com/users/andrixb","html_url":"https://github.com/andrixb","followers_url":"https://api.github.com/users/andrixb/followers","following_url":"https://api.github.com/users/andrixb/following{/other_user}","gists_url":"https://api.github.com/users/andrixb/gists{/gist_id}","starred_url":"https://api.github.com/users/andrixb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andrixb/subscriptions","organizations_url":"https://api.github.com/users/andrixb/orgs","repos_url":"https://api.github.com/users/andrixb/repos","events_url":"https://api.github.com/users/andrixb/events{/privacy}","received_events_url":"https://api.github.com/users/andrixb/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-11-27T17:15:57Z","updated_at":"2018-11-27T20:36:08Z","closed_at":null,"author_association":"NONE","body":"Hi there, \r\n\r\nI hope I'm writing in the right section (otherwise I'll move it wherever it belongs).\r\n\r\nI've been trying to implement the microservice architecture but even though I managed to run two different applications on the same page, I've been struggling a bit to get how to implement a proper routing. \r\nIn the website and in the videos I watched you talk about a top-level routing. Has this to be implemented in NGINX (for instance)? \r\nHow should I use this model if I need to create routes at the component level, like inner/sub-routes?\r\n\r\nMany Thanks, \r\n\r\nA.\r\n"},"comment":{"url":"https://api.github.com/repos/neuland/micro-frontends/issues/comments/442207747","html_url":"https://github.com/neuland/micro-frontends/issues/21#issuecomment-442207747","issue_url":"https://api.github.com/repos/neuland/micro-frontends/issues/21","id":442207747,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0MjIwNzc0Nw==","user":{"login":"adrw","id":8827217,"node_id":"MDQ6VXNlcjg4MjcyMTc=","avatar_url":"https://avatars1.githubusercontent.com/u/8827217?v=4","gravatar_id":"","url":"https://api.github.com/users/adrw","html_url":"https://github.com/adrw","followers_url":"https://api.github.com/users/adrw/followers","following_url":"https://api.github.com/users/adrw/following{/other_user}","gists_url":"https://api.github.com/users/adrw/gists{/gist_id}","starred_url":"https://api.github.com/users/adrw/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adrw/subscriptions","organizations_url":"https://api.github.com/users/adrw/orgs","repos_url":"https://api.github.com/users/adrw/repos","events_url":"https://api.github.com/users/adrw/events{/privacy}","received_events_url":"https://api.github.com/users/adrw/received_events","type":"User","site_admin":false},"created_at":"2018-11-27T20:36:08Z","updated_at":"2018-11-27T20:36:08Z","author_association":"NONE","body":"With https://github.com/square/misk-web, our initial approach has developed into two idioms for sub-routes.\r\n\r\n## 1. Sub-routes can only be extensions of the url domain of the component\r\n\r\n| Component          | Component URL Domain | Allowed Sub-Routes |\r\n| ------------------ | -------------------- | ------------------ |\r\n| `<foo-component/>` | `/foo/`              | `/foo/*`           |\r\n| `<bar-component/>` | `/category/bar/`     | `/category/bar/*`  |\r\n\r\n## 2. Components can not have overlapping url domains.\r\n\r\nAssume in the following example that components are added in the order of the table rows.\r\n\r\n| Component          | Component URL Domain | Url Domain |\r\n| ------------------ | -------------------- | ------------------ |\r\n| `<foo-component/>` | `/foo/`              | Valid           |\r\n| `<bar-component/>` | `/foo/bar/`     | Invalid  |\r\n| `<baz-component/>` | `/category/baz/`     | Valid  |\r\n| `<bip-component/>` | `/category/bip/`     | Valid  |\r\n| `<category-component/>` | `/category/`     | Invalid  |"}}
{"actor":{"display_login":"adrw"}}