Defining content item classes within django-lti would allow for an improved API (specifying properties on init). It would also open the door for broader support of standard content item types and properties, which has been a frequently desired improvement to pylti1p3.
These would act as a replacement for
pylti1p3.deep_link_resource.DeepLinkResource. It seems like the only crucial interface is anas_dictmethod.Defining content item classes within
django-ltiwould allow for an improved API (specifying properties on init). It would also open the door for broader support of standard content item types and properties, which has been a frequently desired improvement topylti1p3.