meta config file format #1
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: JOJ/JOJ3-config-generator#1
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
goal: provide a clear config file format that is easy to manually edit by a TA with not much knowledge
meta config files should be able to handle
refer to https://focs.ji.sjtu.edu.cn/git/JOJ/JOJ3/wiki/JOJ3-Configuration-Schema for more details
at the moment the meta config file does not meet those requirements (to complexe to write and fields missing)
for now focus on:
we can add more options later
IMPORTANT: ignore the following comment, design changed!
from MM:
reference: https://focs.ji.sjtu.edu.cn/git/engr151-24fa/engr151-joj/src/branch/master/home/tt/.config/joj/meta-conf.toml
issue: too much duplicated info (every course will have a "fixed" format of its own). the meta config file should provide a generic format, rather than specifying it for every single tasks
eg. in 151 we should have a list of assignments:
ASSIGNMENTS="h1 h2 h3 h4 h5 h6 h7 h8 p1 p2 p3"
then something like:
h1="1 2 3 4 5 6"
(or h1="1-6" or h1=6 (for exercises from 1 to 6)) andp2="m1 m2 m3"
list of patterns that can be tested on jojon gitea/server the corresponding dir structure would be
h1/1/
contains all files for h1 ex1 andp2/m1
the files for p2m1to run joj students should commit with
joj: h1 2
orjoj: p2 m1
outdated, closing