Server and client implementations must often render similar views. In some places, nearly identical views are generated from distinct Hogan.js and Mustache templates. This task involves reviewing the server and client template usage in MobileFrontend, identifying server and client pairs, and publishing tasks to consolidate each pair. The tasks can be grouped or made distinct per pair depending on complexity and detail uncovered.
Where possible, said tasks should rename Hogan.js and Mustache file extensions to the implementation type, .mustache.
Where server and client deviation is needed, create tasks to separate client view creation from server view parsing and modeling to make view responsibilities distinct. For example, if watchstar.mustache rendered by the server needs to be parsed and modeled by the client for it to render an infinitely scrolling list of watchstars, a WatchstarParser and Watchstar (model) should be separated to distinct module files.
- A table of template pairs is published on this task's description along with any task to consolidate them