You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User is viewing a week with less than 9 someday events
User migrates a someday event forward
The next week already has 9 someday events
The warning alert is shown and the event is not migrated
Current Behavior
1-3: same
4. The event is migrated
5. When going to the next week, all 10 events are rendered
Possible Solution (Not obligatory)
During regular migrations, we use the isAtMonthlyLimit and isAtWeeklyLimit selectors before allowing a migration. Consider creating a new selector called something like canMigrate or isMigrateForwardAllwed, which accepts an argument of "forward" or "backward." It then uses the current viewStart and viewEnd (from redux) and determines whether the operation is acceptable by seeing if the user has less than the limit on the next/previous view.
Context
This bug results in bad UX for users. If they have lots of someday events in the same week, they won't all render properly
The text was updated successfully, but these errors were encountered:
Prerequisites
Expected Behavior
Current Behavior
1-3: same
4. The event is migrated
5. When going to the next week, all 10 events are rendered
Possible Solution (Not obligatory)
During regular migrations, we use the
isAtMonthlyLimit
andisAtWeeklyLimit
selectors before allowing a migration. Consider creating a new selector called something likecanMigrate
orisMigrateForwardAllwed
, which accepts an argument of "forward" or "backward." It then uses the currentviewStart
andviewEnd
(from redux) and determines whether the operation is acceptable by seeing if the user has less than the limit on the next/previous view.Context
This bug results in bad UX for users. If they have lots of someday events in the same week, they won't all render properly
The text was updated successfully, but these errors were encountered: