You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently a lot of Ui components do execute the necessary actions on their own. This was done as a code reuse between mail and search.
Unfortunately, this lead to a few issues:
We trigger the same action from a lot of places (desktop toolbar, mail viewer header, mobile toolbars, shortcuts) and we have to implement the same code a lot of times
When there are differences between mail and search view it complicated the control flow
Instead we would like to pass individual actions to the components that need them and having them implemented at the common ancestor (e.g. top-level view). This means some duplication between mail/search but less duplication for each individual component.
Estimated: 8h
The text was updated successfully, but these errors were encountered:
Currently a lot of Ui components do execute the necessary actions on their own. This was done as a code reuse between mail and search.
Unfortunately, this lead to a few issues:
Instead we would like to pass individual actions to the components that need them and having them implemented at the common ancestor (e.g. top-level view). This means some duplication between mail/search but less duplication for each individual component.
Estimated: 8h
The text was updated successfully, but these errors were encountered: