feat(web): courseStudents query — roster enriched with ZPA (Milestone F5d, Z2)#125
Merged
Conversation
… F5d, Z2)
app.CourseStudents returns a course's roster, each email enriched with ZPA details
(first/last name, gender, group, Matrikelnummer) looked up concurrently (bounded to
8 at a time). A ZPA failure for one student is logged and leaves that entry
un-enriched rather than failing the page; without a ZPA client the roster still
comes back, just plain. Enriched students sort first by last name, un-enriched sink
to the bottom by email. Owner-scoped via a.Course.
GraphQL courseStudents(course): [CourseStudent{email, found, firstName, lastName,
gender, group, mtknr}]. Tested against a mock ZPA (enrich + not-found + ordering),
the no-ZPA path, and auth.
The students page (Z3) renders this; a per-student generated-repos overview (needs
GitLab) is a separate follow-up.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Was
app.CourseStudentsliefert das Kurs-Roster, jede E-Mail mit ZPA-Details angereichert (Vor-/Nachname, Geschlecht, Gruppe, Matrikelnummer), konkurrent abgefragt (max. 8 gleichzeitig). Ein ZPA-Fehler für einen Studi wird geloggt und lässt den Eintrag un-angereichert, statt die Seite scheitern zu lassen; ohne ZPA-Client kommt das Roster trotzdem (plain). Angereicherte zuerst nach Nachname, nicht-gefundene ans Ende nach E-Mail. Owner-scoped.GraphQL
courseStudents(course): [CourseStudent{email, found, firstName, lastName, gender, group, mtknr}]. Getestet gegen Mock-ZPA (Anreicherung + nicht-gefunden + Reihenfolge), No-ZPA-Pfad, Auth.Studierenden-Seite (Z3) rendert das; per-Studi „generierte Repos"-Übersicht (GitLab) ist ein separater Folge-Schritt.
Verifikation
go build/vet (inkl. -tags=integration)/test/golangci-lint— grün.🤖 Generated with Claude Code