-
Notifications
You must be signed in to change notification settings - Fork 2
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
Finish the roundtrip: PL --> MD conversions #86
Comments
Using |
Currently, we can't actually roundtrip learning outcomes field as well as a few other of the fields we include, but are not 1:1 mappings to PL field |
hmmm right. Would you mind making a list of them in this issue so I can try to think about where to put them? |
@firasm so far what I've come across:
From the markdown body itself:
For anything in the markdown body, and potentially in the yaml header, we could also try hiding at the end or in some section of the Attribution I can get from the question.html to get that back, tags are easy enough, I can use a few different methods to remove the autogenerated tags, and topic I can do a similar things from the Footnotes
|
One of the features I really want in the OPB is the ability to convert prairelearn questions into the markdown format. So basically, the reverse of the read_md_problem. This is often called a round trip problem (converting from one file to another, and then that file back to the original)
The reason I want this is because instructors and TAs will often make minor changes to the question.html files, and server.py files to fix bugs during the semester and then forget to make those changes upstream. I know I can enforce it so that they can't edit those files, but a better solution would be to take those files and convert them into md files and then let git deal with diffs and PRs.
Personally, I think if the PL files are well-formed, it should be almost trivial to build a dictionary with all the things from the question.html and info.json and server.py files.
P.S. The more general task (converting any PL question into its markdown version) is probably outside the scope of this project.
The text was updated successfully, but these errors were encountered: