Routing Logic about apprun-realworld-example-app

[yysun]

Routing is event-driven. When AppRun detects the URL hash changes, it fires the events. E.g., for http://.../#/article/{slug}, it fires the # event with the article and the {slug} as the event parameters, so in the src/main.tsx (Line 26), the # event is converted into the /#article event. It leaves the {slug} as the event parameter.

app.on('#', async (route, ...p) => {
  // ...
  app.run(`#/${route || ''}`, ...p);
})

The /#article event actives the ArticleComponent to render the screen.

import app, { Component } from 'apprun';
class ArticleComponent extends Component{
  state = {}
  view = (state) => <div></div>
  update = {
    '#/article': async(state, slug) => {}
  }
}

Basically, the components are sitting there and waiting for their events to come.

[vangelov]

Thank you for your answer!

But what happens if you have two components subscribed to the same event?
You will render both of them in this case.

[yysun]

If they are mounted to different elements. Both will render. But, if the same element, last component wins.

[vangelov]

I see, thank you.

…

On Wed, 27 Jun 2018 at 19:07, Yiyi Sun ***@***.***> wrote: If they are mounted to different elements. Both will render. But, if the same element, last component wins. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACBkI4HaqBzqGPqvvwtb_zPVfb1QlkG5ks5uA63QgaJpZM4U57S6> .