1.7.2 Release

• Performance improvements

1.7.1 Release

• Fixes bootstrapping process.

1.7.0 Release

• Wvr animations have regressed and are no longer firing. (#256)
• SetTimeouts are not performant at load time. (#257)
• Weaver Usage Documentation should include the component template in tab list. (#260)
• Wvr Components should support an extensible list of branded colors. (Primary, secondary, danger, warning... etc). (#262)
• Refactor color usage across wvr components to use branded color list, and include fallback support. (#263)
• Color preview component. (#264)

1.6.0 Release

• Weaver component's build process should build multiple versions of the product. (#86)
• Weaver Usage Docs should be converted into an angular project. (#102)
• The wvr manifest action to submit request should afford providing response map. (#223)
• Handlebars should be extracted into a service and all helpers declared outside of the component constructor. (#232)
• On safari (check firefox) mobile display does not run the position footer function at load time. (#233)
• Weaver components should provide a wvr-cards component. (#234)
• Weaver Component selectors need to be refactored to avoid name collision with Weaver (angularjs) directives. (#237)
• The wvr-header should use the configured asset path for the header logo. (#255)

1.5.0 Release

• Weaver Components should communicate with Weaver web services. (#195)
• Weaver Lists should automatically assign aria owns attribute for each of its list items. (#206)
• Weaver Components should provide an Alert Component. (#207)
• Weaver Components should dynamically assign unique identifiers to each component. (#208)
• Explore ngRX as a state store solution for components. (#209)
• Weaver Components should offer a tabs component. (#210)

1.5.0 Release Candidate

• Weaver Components should communicate with Weaver web services. (#195)
• Weaver Lists should automatically assign aria owns attribute for each of its list items. (#206)
• Weaver Components should provide an Alert Component. (#207)
• Weaver Components should dynamically assign unique identifiers to each component. (#208)
• Explore ngRX as a state store solution for components. (#209)
• Weaver Components should offer a tabs component. (#210)

1.4.0 Release

• Encapsulates bootstrap within global styling
• Performance improvements
• Introduces Mobile Service
• The list item context attr should override the visual context of the list item. (#199)

1.4.0 RC

1.4.0-rc2

Bumped version

1.3.0 Pre-Release

• Weaver Components should have an element query strategy. (#27)
• Icons should be integrated into weaver buttons. (#128)
• Weaver Components should support lists with expanding and collapsing sections. (#163)
• The Wvr Icon component should support animation. (#164)
• Weaver Components should have a list component. (#165)
• Coveralls not providing the coverage notification. (#167)
• Observable subscriptions should be unsubscribed from or converted to promises. (#168)

1.2.0 Release

• Weaver Component should support a global configuration paradigm. (#64)
• Weaver Components should share vendor styling across components. (#82)
• Weaver Components should support multiple font icon libraries. (#85)
• Buttons must be integrated into weaver drop-down. (#129)
• Weaver footer "stick-to-bottom" property affected by wvr-button line-height and padding property. (#150)