Enhance school simulation and management by integrating roster functionality, allowing for the installation and persistence of student and staff data. Update the school architecture to include a roster alongside existing components, ensuring proper validation against map layouts. Revise room definitions to support homeroom designations and update related tests to validate new functionalities and ensure robustness in roster handling.
ci / server (push) Failing after 3m43s
ci / client (push) Failing after 10s

This commit is contained in:
Leonid Pershin
2026-08-18 19:21:40 +03:00
parent e6182e0e45
commit 52c5082418
27 changed files with 732 additions and 66 deletions
+39
View File
@@ -0,0 +1,39 @@
using Arch.Core;
using HSchool.People;
namespace HSchool.Simulation;
/// <summary>Turns roster records into Arch entities. Parents have no map location — by design.</summary>
public static class RosterSpawner
{
public static void Spawn(World world, Roster roster)
{
foreach (var schoolClass in roster.Classes)
{
world.Create(
new ClassIdentity(
schoolClass.Id,
schoolClass.Year,
schoolClass.Letter,
schoolClass.RoomId,
schoolClass.Capacity));
}
foreach (var person in roster.People)
{
world.Create(
new PersonIdentity(person.Id, person.FamilyId, person.Female, person.BirthDate, person.Name),
new PersonBody(person.Numbers, person.Choices),
new PersonSkills(person.Skills),
new PersonTraits(person.Traits),
new PersonNeeds(new Dictionary<string, float>(person.Needs, StringComparer.Ordinal)),
new PersonRoles(
person.IsStudent,
person.IsStaff,
person.IsParent,
person.ClassId,
person.Position,
person.WorkplaceRoomId));
}
}
}