Skip to content

Releases: idootop/nested_scroll_view_plus

v3.1.0

14 May 15:19
a104e09

Choose a tag to compare

  • Fixed a fatal Null check operator used on a null value crash that could occur when a nested scroll position creates a ballistic activity during layout, before applyContentDimensions has completed. Added a haveDimensions guard to both overscroll coordinators so that _getMetrics returns degenerate metrics instead of reading unset scroll extents. (#14 by @smihica)

v3.0.0

20 Jan 16:25
7be1e1e

Choose a tag to compare

  • Synchronized the NestedScrollView source code with Flutter 3.27.2.
  • Added support for CupertinoSliverRefreshControl and other loading indicators.
  • Increased the minimum supported Flutter version to 3.22.0.

v2.0.0

30 Jan 10:59
132e3d0

Choose a tag to compare

✨ New Features

  • Added support for multiple header slivers. (#3)
  • Enhanced the scroll behavior for a smoother and more seamless experience.
  • Synchronized the NestedScrollView source code with Flutter 3.19.0-5.0.pre for better compatibility and performance.

🔧 Fixes

  • Corrected the default physics setting for NestedScrollView.
  • Resolved an issue where NestedScrollView was not adhering to user-specified physics settings. (#4)
  • Improved synchronization between inner and outer scroll views. (#4)

🚀 Upgrade and Migration Guide

With the release of version 2.0.0, there are a few important changes that require action when upgrading from an earlier version.

For Deprecated Widgets:

If you are using OverlapAbsorberPlus or OverlapInjectorPlus in your code, follow these steps:

  • Locate any header slivers wrapped with OverlapAbsorberPlus and remove the OverlapAbsorberPlus wrapper.
  • Remove any OverlapInjectorPlus widget that was placed atop your scroll views.

For OverscrollBehavior:

Search your codebase for any instance of OverscrollType and replace it with OverscrollBehavior. This will ensure compatibility with the new naming convention.

By following these steps, you should be able to smoothly transition to version 2.0.0 without any significant issues. As always, it is recommended to test your application thoroughly after performing an upgrade to ensure that all features work as intended.