-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will be adding your "need" for this pull request in this branch.
Currently I don't plan to address the first two of your nice to haves. However, I would like to mention #25 as a source of info on how to do it.
const response = await services["course-evaluation"].create({ | ||
courseId: code, | ||
reviewDescription: description, | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in relatively low effort, you can do "Auto redirect to new evaluation" using the information you get from this "_id"...
from there...
you could use router = useRouter()
and router.push('coordinator/${_id}')
( i can't do backticks within code highlight)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! I have implemented your requested change
<Datetime | ||
onChange={(date) => { | ||
setDueDate(date); | ||
}} | ||
value={dueDate} | ||
placeholder="13/05/2031" | ||
/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have added your dueDate modal, however, I did notice some discrepancy on the dueDate and the createdAt date... particularly I believe because of different time format.
See #46 , I dont plan to solve that in this pull request, nor in stage 1
Still todo:
Add dueDate field to evaluation document in database to add the ability to set a "due date" for reviewers.
Need:
Nice-to-haves: