Fix bug that left PerDate widget empty when popped to. #5

Merged
marco merged 1 commits from fix-empty-page-bug into master 2024-09-13 14:54:14 +00:00
Owner

Previously, when you would navigate to a PerDate widget that already
exists on the Navigation stack, a food that is entered will not be
visible when popping to the PerDate widget with the same date.

This is because the state is not updated (the BLoC exists per PerDate
widget, and a change in one widget does not cause firing an event in the previous widget's BLoC).

With this fix, we call setState() and update the entries for the widget
from storage.

Previously, when you would navigate to a PerDate widget that already exists on the Navigation stack, a food that is entered will not be visible when popping to the PerDate widget with the same date. This is because the state is not updated (the BLoC exists per PerDate widget, and a change in one widget does not cause firing an event in the previous widget's BLoC). With this fix, we call setState() and update the entries for the widget from storage.
marco added 1 commit 2024-09-13 14:54:09 +00:00
Previously, when you would navigate to a PerDate widget that already
exists on the Navigation stack, a food that is entered will not be
visible when popping to the PerDate widget with the same date.

This is because the state is not updated (the BLoC exists per PerDate
widget, and a change in one widget does not cause firing an event in the previous widget's BLoC).

With this fix, we call setState() and update the entries for the widget
from storage.
marco merged commit 0edb178963 into master 2024-09-13 14:54:14 +00:00
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: marco/calorimeter#5
No description provided.