Web Experience Toolkit - Next Steps
New Plugin Structure
Background
Currently in WET, there is a lot of duplication of code, particularly around plugin initialization and lifetime. Additionally, plugins are sealed in an anonymous scope to prevent conflicts but this approach makes it very difficult for implementers to override or customize plugins. To solve this problem, plugins need to switch to a more open architecture and duplicated code need to be regrouped and shared among plugins. This new structure also need a full unit test suite (see the Unit Testing section for more details). To acheive this goal, several options are available: Prototypal Inheritance (Native), Base2 Library, ES6 Classes w/ Google Traceur