Closed lennemo09 closed 2 years ago
This is what I had in mind! As far as different offerings are concerned, it is a bit more tricky, but I think it should be a list of items e.g [S2-Clayton,S1-Clayton].
This is what I had in mind! As far as different offerings are concerned, it is a bit more tricky, but I think it should be a list of items e.g [S2-Clayton,S1-Clayton].
@saikumarmk Hey there, I've chosen to model the Offerings as a class similar to Requisites but obviously simpler. I thought by doing so we have more flexibility with adding fetcher and helper functions if we were ever to need to do filtering on offerings :D
Thanks Len!
Class to store an unit's information including its requisites using the Requisite subclass. The class is assuming uniqueness of an unit's code (I think we're not going to deal with unit in different offering semesters/years?)
Added some printing helpers for quality of life.