Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat: nicer display of missing (sub)exercises #462

Open
gasche opened this issue Nov 16, 2021 · 1 comment · May be fixed by #485
Open

Feat: nicer display of missing (sub)exercises #462

gasche opened this issue Nov 16, 2021 · 1 comment · May be fixed by #485
Assignees
Labels
kind: feature New user-facing feature.

Comments

@gasche
Copy link
Contributor

gasche commented Nov 16, 2021

Related project scope(s) (ex: client, CSS, grading, etc...) : web frontend, CSS, grading

The problem

If you have several questions inside a single exercise, the display does not feel very nice for students that have only answered a subset of the questions so far: missing questions are displayed in red as "wrong".

Wanted solution

It would be nice if the grader could detect that the question is not "wrong" but "missing", and display it in a more neutral style (gray ?) in the report.

Considered alternatives

It is possible to use different exercises for each question, but not so pleasant. This is what @smdsousa does to avoid the issue.

@gasche gasche added the kind: feature New user-facing feature. label Nov 16, 2021
@erikmd
Copy link
Member

erikmd commented Nov 16, 2021

Thanks @gasche for the suggestion!

I agree that this is something that could be improved (and shouldn't be too difficult to implement at first sight (but I don't assign myself this issue for the moment - lacking of time this week 😅))

− Regarding the alternative you mention, currently it is the standard workaround to limit the size of a grader, indeed;
but note that in the medium term, the nice feature started by @YoanwM (#402) could be a native way to "split a long grader"…

@JossyYila JossyYila linked a pull request May 18, 2022 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: feature New user-facing feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants