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
There is some interest I have in figuring out how to make the Classrooms system work better.
First, Classroom queries only support the type User, not PrivateUser, so a Teacher cannot get sensitive details on their students in a single general query like the one for query classroom(), I'd have to chain the results together and get them later (see #90 for my plan to make query users() accessible for teachers on their students).
Anyway, there must be a way to do at least one of the following two things:
Let teachers get PrivateUser through a query for a Classroom.
Prevent students from looking at fellow students (not just no PrivateUser, no User at all!) through a query for Classroom or through a user() or me() query.
There is some interest I have in figuring out how to make the Classrooms system work better.
First, Classroom queries only support the type
User
, notPrivateUser
, so a Teacher cannot get sensitive details on their students in a single general query like the one for queryclassroom()
, I'd have to chain the results together and get them later (see #90 for my plan to make queryusers()
accessible for teachers on their students).Anyway, there must be a way to do at least one of the following two things:
PrivateUser
through a query for aClassroom
.PrivateUser
, noUser
at all!) through a query forClassroom
or through auser()
orme()
query.Do after #90.
The text was updated successfully, but these errors were encountered: