weblab-staff / submission-portal Goto Github PK

add a for_credit field to the regiration page

We need a mechanism that allows students to lock in their team. We do not have UI in place to do this right now which needs to be designed sooner rather than later.

After students lock in their team they will get a github generated for them!

We also want some setting from an admin page as well that allows us to specify a team-lockin deadline. We also need to bake this notion of team lockin date into backend class settings, so we can auto-generate githubs for the rest.

no bee movie script pls

also dont make it print to console every time it polls pls

maybe make use of node_env var or something cute

needs to be used in:

student view --> adding members to teams

admin view:

• add members to a team
• add students / teams to the email bar on top. Ideally can enter in a kerberos / email / teamname / student first name / lastname.
• adding admins to the class

Also ideally can be integrated / shared code with the filter for students in the teams/student view.

current mechanism totally ignores those users which is wrong. The /api/class/class_id/add-admin route relies upon the fact that the user has registered under the new active-year. This route is different as those users do not exist yet. Maybe the solution for this lies in user registration. I see two options:

1. Check on user registration if any previous user documents exist for that github username, and if there are check if any of them has admin status (and if they do set the new user to have admin status by default). If we did this then we would not need to specify admins when creating a new class. This assumes some admins will carry over year to year.

2. Upon user registration check to see if the admins for the current_year has that user's github username in the list of admin github usernames. If so, give them admin privs. This is probably the cleaner solution?

Opinions @cory2067 ?

currently after clicking send email the window just hangs and its unclear if the website crashed or the email sent.

Current sorting for submissions is based on team creation time? There should be some better default sorting, or some way to set the sort.

related to generic search but is easier and should be done before generic search complete

expected behavior: click on milestone 2 icon in grading panel, and the UI opens milestone 2
observed behavior: click on milestone 2 icon, and the UI opens milestone 0

registration should poll /whoami and pre-fill the first name and last name fields which are currently extracted from github.

https://github.com/weblab-staff/submission-portal/blob/master/server/github.js#L9
i still get auto-added to every team
change this to some current staff's username

Probably due to some UTC conversion stuff.
For example, if you make a new milestone due on 1/8, it shows up as due 1/7.

We can work around this by setting the due date as +1 day in the future

basically change icon to a minus sign or something similar so it's clear you are deselecting everything

Not sure if this filter should happen on the frontend or backend, but we should have some easy way to see only submissions that don't have feedback for milestone X yet

also this is a soft-cap it shouldn;t prevent you from having >cap size teammates, but just render a warning that they cannot compete like that.

there are surprisingly many teams that end up becoming empty

useful note for error handling with async/await: https://thecodebarbarian.com/80-20-guide-to-express-error-handling

1. Add to students/teams view. Right now, the email button just says alert("email") and does nothing
2. Change milestone grading view to show a mailto instead of that feedback form

something something react router can see what shannen did in her code.

instead of having user enter in sheet id manually l o l