Dead Code in Einreichungen
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reviewing issue #18, especially its fifth option, and trace how submissions for exercise subparts are handled. Define the detectable dead-code cases and configurable rejection behavior before locating the relevant implementation and tests; done means the stated misuse cases can be rejected when enabled without rejecting valid submissions.
Written by the indexing model from the issue text.
Description
... könnte erkannt und (eventuell konfigurierbar) zurückgewiesen werden.
Beispiel: Bei Teilaufgaben einer Übungsblatt-Aufgabe werden alle Teile bei einer Autotool-Aufgabe eingereicht statt separat bei den "Unteraufgaben". Das könnte dann zurückgewiesen werden.
weiteres Beispiel: Wenn in https://github.com/fmidue/prolog-programming-task/issues/18#issue-2772197577 auch die 5. Option umgesetzt wird, könnte verhindert werden, dass Studierende einfach noch eine separate Regel a :- a. hinzufügen, um Verwendung von Rekursion vorzutäuschen.
- Dominant language
- Haskell
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fmidue/prolog-programming-task
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
fmidue/prolog-programming-task#36 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
All issues in fmidue/prolog-programming-task