Enhance timetable functionality and UI integration
- Updated protocol documentation to include new `classId` and `roomLabel` fields in the timetable API responses. - Added classes and rooms to the timetable response structure, improving data accessibility for client applications. - Enhanced the UI components to display timetable information, including class and room details, in the management and people panels. - Implemented functionality to fetch and display personal timetables for individuals, ensuring a comprehensive view of schedules. - Revised localization strings to support new timetable features and improve user experience. - Added tests to validate the new timetable functionalities and ensure robustness in handling timetable data.
This commit is contained in:
@@ -111,10 +111,18 @@ internal static class TimetableEndpoints
|
||||
var roster = published.Roster ?? new Roster([], [], []);
|
||||
if (published.Catalog is null)
|
||||
{
|
||||
return new TimetableResponse(weekDays, 0, [], []);
|
||||
return new TimetableResponse(weekDays, 0, [], [], [], []);
|
||||
}
|
||||
|
||||
return TimetableMapper.From(table, roster, published.Catalog, weekDays, locale, classId, personId);
|
||||
return TimetableMapper.From(
|
||||
table,
|
||||
roster,
|
||||
published.Catalog,
|
||||
published.Map,
|
||||
weekDays,
|
||||
locale,
|
||||
classId,
|
||||
personId);
|
||||
}
|
||||
|
||||
private static IResult TimetableResult(
|
||||
|
||||
Reference in New Issue
Block a user