For issue #14
The SearchResults component displays the results of a websoc search. It has 2 components that work with it but one of those components aren't only used in SearchResults which is why i put them all under a SOC folder (The CourseDetails component will use the SOC/CourseOfferings component). Basically the SearchResults get an array of results where each element is an object that has the dept/num/name of a course along with an array of offerings, each of those course objects are passed to the CourseResults component which then creates a header and passes all the offerings to the CourseOfferings component which then renders the table and the actual offering details, if you go to UCI WebSoc and do a general search on a department this will make sense, basically SearchResults is the entire results page, CourseResults are the specific course sections and CourseOfferings are the rows underneath the course title headers.
For issue #14 The SearchResults component displays the results of a websoc search. It has 2 components that work with it but one of those components aren't only used in SearchResults which is why i put them all under a SOC folder (The CourseDetails component will use the SOC/CourseOfferings component). Basically the SearchResults get an array of results where each element is an object that has the dept/num/name of a course along with an array of offerings, each of those course objects are passed to the CourseResults component which then creates a header and passes all the offerings to the CourseOfferings component which then renders the table and the actual offering details, if you go to UCI WebSoc and do a general search on a department this will make sense, basically SearchResults is the entire results page, CourseResults are the specific course sections and CourseOfferings are the rows underneath the course title headers.