Skip to content

Releases: ghiscoding/slickgrid-universal

v5.7.0

14 Sep 16:28
Compare
Choose a tag to compare

5.7.0 (2024-09-14)

A huge thanks to @Vsinghal339-source for all the troubleshooting and PRs to improve performance of the grid, there were couple of area with code of O(n square) that were brought down to of O(n), it's really great to receive such huge impacting contributions. Thanks a lot 🎉

Features

Bug Fixes

Performance Improvements

v5.6.1

31 Aug 15:42
Compare
Choose a tag to compare

5.6.1 (2024-08-31)

Bug Fixes

v5.6.0

24 Aug 17:08
Compare
Choose a tag to compare

5.6.0 (2024-08-24)

Release Info

With this release, we are migrating to the original Vanilla-Calendar-Pro project and dropping the vanilla-calendar-picker temporary fork and that is because all features & bug fixes I had in my fork were all merged recently to the original project (the fork was always meant to be a temporary thing).

There's also a new rowTopOffsetRenderType grid option that might be of interest, the default is top but if you set it to transform then all rows of the grid will use transform: translateY({offset}px) to position each row in the grid and the transform might actually improve perf as per this article: Why Moving Elements With Translate() Is Better Than Pos:abs Top/left

Features

Bug Fixes

Performance Improvements

v5.5.2

17 Aug 15:38
Compare
Choose a tag to compare

5.5.2 (2024-08-17)

Bug Fixes

  • use setTimeout/setInterval from window object with correct TS type (63953ec) - by @ghiscoding

v5.5.1

17 Aug 02:53
Compare
Choose a tag to compare

5.5.1 (2024-08-17)

Bug Fixes

v5.5.0 - Infinite Scroll

07 Aug 00:22
Compare
Choose a tag to compare

5.5.0 (2024-08-07)

Release Info

This new release adds the Infinite Scroll feature and with it adds not just 1 but 3 new examples to cover all use cases (read the new Infinite Scroll docs for more info)

  1. Example 26 - with OData Backend
  2. Example 27 - with GraphQL Backend
  3. Example 28 - with JSON data (local)

Infinite scrolling allows the grid to lazy-load rows from the server when reaching the scroll bottom (end) position. In its simplest form, the more the user scrolls down, the more rows get loaded. If we reached the end of the dataset and there is no more data to load, then we'll assume to have the entire dataset loaded in memory. This contrast with the regular Pagination approach which will only hold a single page data at a time.


Features

Bug Fixes

  • core: pinning 1st column could caused the header to get misaligned (42c94e8) - by @ghiscoding
  • styles: Add missing semicolon in line 1147 of _variables.scss (36c3187) - by @oilmonkey

v5.4.0

20 Jul 16:02
Compare
Choose a tag to compare

5.4.0 (2024-07-20)

Features

Bug Fixes

v5.3.4

13 Jul 17:38
Compare
Choose a tag to compare

5.3.4 (2024-07-13)

Bug Fixes

  • styling: fix SASS warnings for declarations mixed with nested rules (de9460d) - by @ghiscoding

v5.3.3

06 Jul 00:06
Compare
Choose a tag to compare

5.3.3 (2024-07-06)

Bug Fixes

v5.3.2

29 Jun 01:15
Compare
Choose a tag to compare

5.3.2 (2024-06-29)

Bug Fixes