The MIT Registrar defines a strict syntax for course requisites. It's the adherence to this strictness which has made CourseRoad possible, by allowing the automated parsing of those requirements.
Starting in Spring 2018, some classes began using an alternate syntax for their requisites, which relies on the use of nested parentheses. Example: (6.041B, 18.05, or 18.600) and (18.06, 18.700, or 18.701)
parseRequisites, whose core logic hasn't really changed since the initial commit in May 2012, doesn't know what to do with this, and is incorrectly parsing the parentheses as part of the course names. This is causing breakage downstream, as the prereq-line-drawing UI code tries to find classes with invalid names.
9b6a5fb2425ed5b8502757dee5345336446a69f1 patched this to prevent said UI breakage but we'll need to write a better requisite parser than whatever freshman!Danny could manage in 2012 :P
The MIT Registrar defines a strict syntax for course requisites. It's the adherence to this strictness which has made CourseRoad possible, by allowing the automated parsing of those requirements.
Starting in Spring 2018, some classes began using an alternate syntax for their requisites, which relies on the use of nested parentheses. Example:
(6.041B, 18.05, or 18.600) and (18.06, 18.700, or 18.701)parseRequisites, whose core logic hasn't really changed since the initial commit in May 2012, doesn't know what to do with this, and is incorrectly parsing the parentheses as part of the course names. This is causing breakage downstream, as the prereq-line-drawing UI code tries to find classes with invalid names.9b6a5fb2425ed5b8502757dee5345336446a69f1 patched this to prevent said UI breakage but we'll need to write a better requisite parser than whatever freshman!Danny could manage in 2012 :P