PERMANENT BACKLOG
All functionalities must be created across all ends in order for full integration to occur, such as the implementation of the conversations page, API calls to post and get information, etc. There is a current iteration of a currently working full-stack branch with the current functionalities. Until all aspects of the integration are complete, this issue will remain backlogged.
UC currently does not support a log in functionality, and very limited user functionality. The logged in user is hard-coded by default, and cannot enroll in new courses. Furthermore, RS does not enable a scenario to be added for a particular course. For these reasons, this past week's demo was partially strung together by calling some SQL queries in advance to create a course, link the course to the student. When the scenario is created (RS), it is by default added to this aforementioned course, where it is rendered on the UC front-end. As we can see, this is by no stretch of the imagination a robust flow. In the interest of building said flow, I propose we develop a schedule that pertains to all members of the track, so that we can incrementally release new features in a structured format.
PERMANENT BACKLOG All functionalities must be created across all ends in order for full integration to occur, such as the implementation of the conversations page, API calls to post and get information, etc. There is a current iteration of a currently working full-stack branch with the current functionalities. Until all aspects of the integration are complete, this issue will remain backlogged.
UC currently does not support a log in functionality, and very limited user functionality. The logged in user is hard-coded by default, and cannot enroll in new courses. Furthermore, RS does not enable a scenario to be added for a particular course. For these reasons, this past week's demo was partially strung together by calling some SQL queries in advance to create a course, link the course to the student. When the scenario is created (RS), it is by default added to this aforementioned course, where it is rendered on the UC front-end. As we can see, this is by no stretch of the imagination a robust flow. In the interest of building said flow, I propose we develop a schedule that pertains to all members of the track, so that we can incrementally release new features in a structured format.