Changelog

[2.0.5-rc.2] - 09-13-24

Resolves

• Downgrading Angular dependencies to 12.2.16 to fix npm build.
• Added "cheerio": "1.0.0-rc.10" to resolve issues with the compodocs command not running correctly.
• Added "typescript": ">=4.2.3 <4.4" to fix npm build.
• Added "whatwg-mimetype": "^3.0.0" to fix npm build.

[2.0.5-rc.1] - 12-02-22

Resolves

• WYSIWYG save is not working. (#516)

[2.0.4] - 11-15-22

Resolves

• Remove the "upgrade" button from the tinymce editor. (#512)
• Locked the node version to 16. (#515)

[2.0.3] - 10-12-22

Resolves

• Fix bad error handling and reporting wvr-button. (#504)
• Footer Becoming Sticky when it should not. (#503)
• Remove ng-inline-svg as it is no longer maintained. (#502)
• Redesign dependency list, reducing dependencies where possible. (#507)
• Fixed tabs to no longer need a wrapping div to display content. (#505)

[2.0.2] - 09-19-22

Resolves

• Normal mouse clicks do not work for certain designs with drop-down menus following the 2.0.1 release.

[2.0.1] - 09-15-22

Resolves

• Local npm via Verdaccio and SASS Migrator. (#472)
• The mobile menu slide out tray continues to allow links to be clicked on when closed. (#474)
• Avoid replaceChild() and restructure projection function. (#479)
• Collapsible Card is not completely collapsible. (#483)
• Directory UI - bottom-nav items (left most) is seen to have shifted left. (#482)
• Add in-code documentation for the README.md. (#484)
• Build components with Node 16 or greater. (TAMULib/tamu-library-components#429)
• Update deprecated karma coverage package. (#306)
• ADA - Buttons missing label and expand/collapse notification. (TAMULib/tamu-library-components#423)
• Issue 4: Focus indicator missing. (TAMULib/tamu-library-components#425)

[2.0.0] - 10-29-21

Resolves

• 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)
• Memory Leak And Performance degradation when components is left open. After about 2 hours Gigibytes of memory in use. (#438)
• Incorrect boolean logic in dequeue and inadequate tests (#442)
• The tabs component should support theming (#348)
• Incorrect manifest entries are being updated in Manifest. (#439)
• The tabs component should support theming (#348)
• Incorrect manifest entries are being updated in Manifest. (#439)
• Weaver Card hardcodes width as a style. (#451)
• Weaver Components should provide a Message Receiver Component (#407)
• Weaver Card Should Support Expand/Collapse on Card Header click. (#445)

[1.12.0] - 06-04-21

Resolves

• The mobile service should use the ngrx store to maintain state. (#333)
• Weaver Components should use an alternate mechanism to display: none when components are ready (#363)
• Weaver Components should use Ngrx to to maintain state. (#364)
• Weaver Components should build without warnings (#365)
• Refactor Template Service to Template Utility (#379)
• Refactor to pure pipes (#380)
• Remove isMobileAgent from base component (#381)
• Refactor mobile store to layout store (#382)
• Afford input text color on text component (#388)
• Colors in color utility should be brought in via JSON (#390)
• Weaver Components Manifest should support path variables (#398)

[1.11.1] - 05-19-21

Resolves

• Weaver Components should use an alternate mechanism to display: none when components are ready (#363)

[1.11.0] - 05-12-21

Resolves

• The weaver modal bg should be displayed (and NOT flicker). (#328)
• Weaver modal only opens when a single modal is used. (#346)
• Weaver components should offer a default theme group (modeled after btn). (#347)
• The Card Component should support theming. (#350)
• Lighthouse build failing for weaver components. (#356)

[1.10.0] - 04-23-21

Resolves

• Weaver Modal button should be toggle-able. (#329 )
• WVRWYSIWYG is not appearing in the usage documentation. (#330 )
• WVR Theme Variants should be expanded to include all needed variant names. (#334)
• Weaver Component's Modal Component should utilize the wvr-button-component intead of the wvre-button. ( #341)
• Weaver component should provide additional theme variants. ( #342)
• Weaver drop down menu should have a delay on hover prior to displaying the dropdown menu. ( #344)

[1.9.0] - 03-31-21

Resolves

• Weaver Components should provide a modal component. (#314)
• Weaver Components should offer a WYSIWYG component. (#315)
• Weaver Button should be able to trigger actions on a parent component. (#319)
• Weaver WYSIWYG should maintain state using NgRX (#322)

[1.8.0] - 12-18-20

Resolves

• Weaver Components should utilize externals to reduce bundle size. (#158)
• Remove scss, rendered unnecessary by the recent theme features. (#276)

[1.7.4] - 12-15-20

Resolves

• Patch icon bug

[1.7.3] - 12-15-20

Resolves

• Fixed SVG styling and performance.

[1.7.2] - 12-14-20

Resolves

• Performance improvements

[1.7.1] - 11-20-20

Resolves

• Fixes bootstrapping process.

[1.7.0] - 11-20-20

Resolves

• 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] - 11-2-20

Resolves

• 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] - 10-8-20

Resolves

• 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] - 9-23-20

Resolves

• 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.3.0] - 08-13-20

Resolves

• 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] - 07-16-20

Resolves

• 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)

[1.1.0] - 06-25-20

Resolves

• Wvr Components should provide a wvr-button component (#103)
• CDN needs to be exposed through the firewall (#135)
• Fix Z-Index on dropdown overlaps (#133)
• Restore dynamic change detection for display of bottom nav (#136)
• Dropdown inside of List inside of Header flickers instead of staying open (#119)

[1.0.0] - 06-11-20

Resolves

• The wvr-header should support mobile and tablet layouts (#7)
• Weaver Components should have CI hooks for lighthouse (#105)
• wvr-component should have attribute: page-title-url (#116)
• Weaver Drop down component selector should be renamed (#125)

[0.0.5] - 05-14-2020

Resolves

• The wvr-header should support accessible designs (#8)
• Weaver Components should provide a drop down element (#20)
• The wvr-header component's bottom-nav section should display conditionally (#81)
• Weaver components usage documentation fails to build (#83)
• Weaver documentation landing page is broken (#84)
• wvr-footer's navbar should be have a height of 100% (#89)