flipbase / backbase Goto Github PK

Add methods like beforeRender, afterRender, beforeRemove and afterRemove to improve handling of components' lifecycle.

Backbase should be optimised for lower-end JavaScript runtime environments as well.

Instead of using a meditator pattern we should use a singleton that handles events on top level, like state. Why?

1. The app can be rerender using the exact same state. Which is beneficial for testing but also debugging purposes. We can just send the state object to a debug API endpoint.
2. Centralizes event handling. Currently event handling is included on a instance. But events have more impact on a single component. Which event is triggered from what component might be unclear. Using a central point where the complete configuration solves this problem partly (now you know only which events might be triggered).
3. At this moment we don't have an overview of which events are triggered.

Research:

• Should we also include a virtual DOM?