Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dashboard overhaul #186

Merged
merged 23 commits into from
Oct 16, 2024
Merged

Dashboard overhaul #186

merged 23 commits into from
Oct 16, 2024

Conversation

charliemirabile
Copy link
Contributor

After one year, we have finally surpassed what we had for a dashboard

This was referenced Oct 14, 2024
charliemirabile and others added 17 commits October 14, 2024 18:49
To make way for a more proper dashboard that shows the grades, we should
move the old dashboard that shows all submission activity to a new url
fixes a flake8 error; improves legibility.
Lists all assignments with placeholder table headings.
Right now the post request handler just logs which assignment the oopsie
was requested for.
Add a page that sits between clicking the oopsie button and
actually using the oopsie where the student can think twice.
also the oopsie table will be keeping track of the time
stamp it recieves the oopsie at: the user won't ever need this
info but it might be useful for administrative reasons.
verify that the provided assignment is valid and that it is not too late
to use an oopsie for that assignment, and then once the student confirms,
record their request in the database.
We will want to add more complexity and doing it inline would make the
HTML code unwieldy.
Determine 'oopsieness' and store that value in each assignment table.
This value is used to change how the oopsie button is generated.
add more table header entries to represent the fields that will be in an
assignment submission, and introduce a new function to generate a row for
a submission, and use to create one for the initial submission.
Use the gradeable row function to create rows for the peer reivew and
and final submission along with the other components of the full table
layout.
If an oopsie was used, do not show the initial submission or peer
review fields to the user for that particular assignment.
The main submission table is filled with every 'email event' that
mailman sees, the gradeable table is the place for keeping track of
all submissions that on the surface appear to be 'good' submissions:
they are addressed to the correct emails, they are submitted within
the expected submission windows, etc.
This will record the fate of the submission during mailman's processing
If this submission is ineligible for grading, this field will hold the
reason why. If it is an eligible submission, this field will explain
what the mailman thinks it is.
This lays the groundwork for future mailman processing that will
recognize valid submission attempts and provide useful feedback
to the user.
orbit/radius.py Outdated Show resolved Hide resolved
mailman/submit.py Outdated Show resolved Hide resolved
michael-burke4 and others added 6 commits October 15, 2024 20:04
Update the submission's status to reflect this processing
Update the submission's status to reflect this processing
The table now handles the possibility that there are any number of peer
review assignments between 0 and 2.
If a submission is provided (currently none is - all callsites just pass
None) the table displays the timestamp and submission ID.
until the student makes an initial submission and the initial submission
deadline has passed, it does not make sense to display all the rows of
the table, because the peer review will not be filled in, and the student
may not be eligle for making a final submission if they do not make an
initial one.
Copy link
Contributor

@theyoyojo theyoyojo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants