You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of the currently existing build warnings will be fairly difficult to fix without some minor changes to code organization for the StudentData class and its interactions with the LMSAssignmentManager interface. In particular, the isStudentFolderPresent method is part of the LMSAssignmentManager.
Both StudentData and LMSAssignmentManager are generic and have related type parameters.
Many uses of LMSAssignmentManager should be LMSAssignmentManager<?> - wildcarded.
This causes serious conflicts with attempts to wildcard StudentData... which should probably not be generic at all.
As a result, LMSAssignmentManager.isStudentFolderPresent should be reworked to StudentData.getStudentFolder. The LMSDataTag inner class/interface of LMSAssignmentManager could prove useful in rerouting the important functionality to facilitate this restructure.
Alternatively, if it is possible to reasonably preserve the current generic specifications while being more precise in their use, that would be ideal.
The text was updated successfully, but these errors were encountered:
Some of the currently existing build warnings will be fairly difficult to fix without some minor changes to code organization for the
StudentData
class and its interactions with theLMSAssignmentManager
interface. In particular, theisStudentFolderPresent
method is part of theLMSAssignmentManager.
StudentData
andLMSAssignmentManager
are generic and have related type parameters.LMSAssignmentManager
should beLMSAssignmentManager<?>
- wildcarded.StudentData
... which should probably not be generic at all.As a result,
LMSAssignmentManager.isStudentFolderPresent
should be reworked toStudentData.getStudentFolder
. TheLMSDataTag
inner class/interface ofLMSAssignmentManager
could prove useful in rerouting the important functionality to facilitate this restructure.Alternatively, if it is possible to reasonably preserve the current generic specifications while being more precise in their use, that would be ideal.
The text was updated successfully, but these errors were encountered: