removed timetable limits, fully dependent on marianumConnect now
This commit is contained in:
@@ -17,6 +17,10 @@ class CapabilitiesCubit extends HydratedCubit<CapabilitiesState> {
|
||||
|
||||
bool get canReceivePushNotifications => state.pushNotifications;
|
||||
|
||||
int? get timetablePastDays => state.timetablePastDays;
|
||||
|
||||
int? get timetableFutureDays => state.timetableFutureDays;
|
||||
|
||||
/// Refreshes capabilities from the server. On any failure (endpoint not yet
|
||||
/// live, network error, 4xx) the previously hydrated flags are kept but the
|
||||
/// state is marked `loaded` — a failed fetch never silently grants a
|
||||
@@ -32,6 +36,8 @@ class CapabilitiesCubit extends HydratedCubit<CapabilitiesState> {
|
||||
CapabilitiesState(
|
||||
viewForeignTimetables: response.viewForeignTimetables,
|
||||
pushNotifications: response.pushNotifications,
|
||||
timetablePastDays: response.timetablePastDays,
|
||||
timetableFutureDays: response.timetableFutureDays,
|
||||
loaded: true,
|
||||
),
|
||||
);
|
||||
|
||||
Reference in New Issue
Block a user