INGInious / INGInious/problems-blockly

file names in blockly tasks

Offen
#16 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
JavaScript
Sterne
2
Forks
4
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

In the subproblem editor, there shoudn't be sections to insert files. The files should have fixed names and be edited in the "Task Files" tab. The names of the files should be suffixed with the subproblem id so that we can have more than one subproblem in one task :

- "Files (Interpreter, Visual execution)" : There should be only one file named by example visual-SUBPROBLEM_ID.js containing the interpreter code + the animation specific code. The name of this file should be fixed and documented.

and

- "Additional blocks files" : This file should also have a fixed name or depending on the implementation choice in https://github.com/UCL-INGI/INGInious-problems-blockly/issues/15 a file containing only the stubs generated by the blockfactory to be added in the workspace later.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

Start by reviewing the subproblem editor and the "Task Files" tab, then read issue #15 for the implementation dependency. Done means removing file-insertion sections, using fixed names suffixed with the subproblem ID for the visual and additional block files, and documenting those names.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
javascript
Bereich
frontend
Issue-Typ
Feature
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.