We’ve seen some annoying bugs as a result of events being fired twice, or in a circular event chain.
Update loops are one of the problems that React explicitly aims to solve and Flux explicitly disallows actions triggering other actions to avoid this.
For example, we currently have two components, search and compose, which use Twitter’s typeahead search. Our typeahead data module sends out events like this:
Mendeley's flight-autocomplete component appears to follow the same event naming scheme
Event namesI’m not sure we’ve got our event-naming nailed as yet. In fact, our naming conventions seem to be widely disagreed upon within our small team. Despite that, we seem to be managing pretty well.
Useful reference for Flight idioms from TweetDeck