[Frontend/Course Admin] Additional fields feature#825
Conversation
|
Please separate a) and b) so that the review of b) can be done easier, as a) review should be quite straightforward. |
a86b49a to
c763035
Compare
|
A part is now in PR #841 |
|
Can you rebase this PR now ? |
c763035 to
41bde36
Compare
ddec9cf to
aee2176
Compare
6755ba0 to
dd5c8c2
Compare
anthonygego
left a comment
There was a problem hiding this comment.
You are never parsing and loading the fields into the course object, neither here or in #832. This will therefore never check YAML validity.
This is done for tags here: https://github.com/UCL-INGI/INGInious/blob/c9f38af3a72e6fa98dcd01004e3075a335483933/inginious/frontend/courses.py#L82
Your are therefore using get_course_descriptor_content in #832 to access the data which should only be used to populate the dictionary before dumping to YAML file. The OOP principles are already too poorly respected in the code to worsen it.
9e4d381 to
861715f
Compare
Mistake about dict content path.
40125ee to
77ae877
Compare
Add check to verify that the value is actually valid and raise an exception if this is not the case.
a) Move tags page
b) add "additional fields" feature