Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: adding two and more items atop visible area causes jump #5

Merged

Conversation

radomir9720
Copy link
Owner

Status

READY

Description

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore
  • 📏 Test
  • 📑 CI

* docs: write docstrings for DefaultItemsNotifier and ItemsEntity
* chore: remove ItemsBuildQueueMixin, as it is not used anymore
…noreCondition

* refactor: added ability to pass boolean to StaticPointerIgnoreCondition
* docs: written docsstrings for StaticPointerIgnoreCondition
* docs: document all public members
* chore: rename AlwaysFalsePointerIgnoreCondition to StaticPointerIgnoreCondition
* refactor: removed unused AnimationControllerConfig.postframeCallback parameter
* feat: added extensions on EventController for easily adding new events
…eNotifyOnMove parameter to forceNotifyOnMoveAndRemove

* fix(widgetbook_app): set forceNotifyOnMoveAndRemove to true for GridView and PageView
* chore(widgetbook_app): override equality operator of MyModel
@radomir9720 radomir9720 self-assigned this Mar 23, 2023
* chore: deleted publish_to parameter from pubspec.yaml
@radomir9720 radomir9720 merged commit c25cd42 into main Mar 26, 2023
@radomir9720 radomir9720 deleted the fix/adding_two_and_more_items_atop_visible_area_causes_jump branch March 26, 2023 12:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant