TAMULib / weaver-components

Custom Web Components for the Weaver UI
MIT License
0 stars 1 forks source link

Sprint21 staging #436

Closed rmathew1011 closed 2 years ago

rmathew1011 commented 2 years ago

Weaver Components should have a consistent content projection strategy. (#236) Convert wvre-tab to pseudo element. (#308) Card component needs redesign to avoid local state from DOM inspection. (#387) Weaver Components should expose the manifest entry request through its public api. (#405) Extract CSS to avoid the removal of deprecated style strategy. (#408) Weaver Tabs should utilize the new content projection strategy. (#410) Weaver Components Card Component should utilize the content projection strategy. (#414) Weaver Components dropdown should utilize common content projection to afford two-way binding. (#417) Weaver Components should support two way binding to angularjs scope. (#421) Weaver Components should delay bootstrapping until a specified condition has been met. (#425) Weaver Components Memory and Performance Concerns. (#428) Weaver Components should compile using the ivy partial compiler option. (#430)