In this pull request, two pages have made significant progress:
/user-disp-test/
Used essentially as a dashboard proof of concept. Actual styling details will be worked out later. This is a working version of how data could be displayed. Remaining things to work out:
Redirect to classes (student)
Redirect to classes (leader)
More progress on the leader redirect will be made once the seating chart code works well
/assignment-data?id={assignmentId}
Using a query parameter on the frontend, from that dashboard page, a fetch is made to the backend to save specific assignment data. Remaining things to work out:
Assignment attachments (waiting for backend progress)
Differentiating Assignment (parent) and Quiz (subclass) on dashboard and in redirect
Overall Notes
It is most important to note that the dashboard will work by using the JWT and a specific fetch request to identify the person and send the class data, not their ID as a query parameter (as is the current method for debugging). This will all be properly implemented once the JWT problems stop happening.
In this pull request, two pages have made significant progress:
/user-disp-test/
Used essentially as a dashboard proof of concept. Actual styling details will be worked out later. This is a working version of how data could be displayed. Remaining things to work out:
More progress on the leader redirect will be made once the seating chart code works well
/assignment-data?id={assignmentId}
Using a query parameter on the frontend, from that dashboard page, a fetch is made to the backend to save specific assignment data. Remaining things to work out:
Overall Notes
It is most important to note that the dashboard will work by using the JWT and a specific fetch request to identify the person and send the class data, not their ID as a query parameter (as is the current method for debugging). This will all be properly implemented once the JWT problems stop happening.
We've effectively shown our progress toward connective functionality!