To improve performance in react redux applications
published 1.0.3 4 years agoNormalizes JSON according to schema for Redux and Flux applications
published 1.0.2 3 years agoclient utilities for date and time conversions
published 1.0.0-beta.10 a year agoGeneralized Contract for the events from Marketplace App, In-App widgets, CRM-Plus and EFC
published 0.0.1-beta.29 4 months ago- published 0.0.1-beta-2 3 years ago
- Persisting time value in timer detail on mount # 0.0.1-beta-6 - Performance fix - Update AutoPauseEnabledIds only if it is not already added.
published 0.0.1-beta-7 2 years agoCollection of components that can be used to improve performance
published 0.0.1-beta.8 3 months agoGeneralized Contract for the events from Marketplace App, In-App widgets, CRM-Plus and EFC
published 0.0.1-beta.9 4 years ago- published 1.0.0 4 years ago
1. History object is a side-effect. If you are using redux then handle history object inside middleware. Don't flow over component. In react-router, histroy object flow over component via context. All Link(withRouter) component more couple with router. I
published 1.0.0-beta.28 2 years ago* **Widgets rendering and actions handle globally for all the themes** * **Schema verification for the get,set and event,hooks request and responses** * **All the marketplace extensions related functionality handled and provding the data for the UI. Use
published 1.0.10-beta.11 a year ago- published 0.0.0-temp-3 3 years ago
Use Multiple Contexts, and keep state close to its Dependent Components
published 0.0.23 2 years agoIn this Package, We Provide Some Basic Components For Accessibility
published 2.2.1 a month ago