API request: Course JSON with participants and their exercise status
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 38/100
Línea de trabajo
Start by reading the existing /:instanceId/courses/:courseId/points.json, exercise_status/:studentId.json, and /:instanceId/participants.json API entry points. Trace how each supplies course participants, student information, and exercise status. Done means /:instanceId/courses/:courseId/participants.json returns the course id and each participant with the proposed information and exercise-status fields in one response.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
There's a need for better API in TMC Server for resolving which students have been in a specific course and what is their exercise status. Now to get students of a specific course from TMC you need to navigate to
/:instanceId/courses/:courseId/points.json
and get student IDs from "users" attribute.
On the other hand, you can get exercise status from
/:instanceId/courses/:courseId/exercise_status/:studentId.json
Finally, for complete student information you need to get them from
/:instanceId/participants.json.
To solve all of this with just one request, we suggest the following path:
/:instanceId/courses/:courseId/participants.json
which returns something like this:
{ "id": "courseId", "participants":
[
{ "id": "1", "username": "name", "first_name": "first", "last_name": "last",
"exercise_status": [
{ "exercise1": "status" }, { "exercise2": "status" }
]
}
]
}
This way we can easily find out which students are in the course, their information and which exercises they have been working on.
- Lenguaje dominante
- Ruby
- Estrellas
- 51
- Forks
- 42
- Merge medio
- 1 h 27 min
- PR fusionados (30 d)
- 1
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de testmycode/tmc-server
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
testmycode/tmc-server#590 ·
-
Exercise Submission Failed Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 20/100
testmycode/tmc-server#576 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
testmycode/tmc-server#488 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
testmycode/tmc-server#487 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
testmycode/tmc-server#477 · 2 comentarios ·
Todos los issues de testmycode/tmc-server
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Please Drop ruby 3.2 support Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
googleapis/google-api-ruby-client#28001 · 5 reacciones ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100