When creating a term,subject,grade type etc the createdOn shouldn't be settable by the user code of the GradesService. We might either decide that the creation functions offer only attributes that the user code is allowed to set (e.g. createdSubject shouldn't have a parameter createdOn, which might mean splitting models - SubjectCreate) or throwing if the createdOn attribut of a model that is passed to the creation functions is set.
When creating a term,subject,grade type etc the
createdOnshouldn't be settable by the user code of theGradesService. We might either decide that the creation functions offer only attributes that the user code is allowed to set (e.g.createdSubjectshouldn't have a parametercreatedOn, which might mean splitting models -SubjectCreate) or throwing if thecreatedOnattribut of a model that is passed to the creation functions is set.