[UI/UX:Submission] "My Late Days" Page Update#12361
Conversation
- Added explanation of table for user to better understand how to read the table - Added users # of late days at the top, so when users click "My Late Days", the first thing they see is how many late days they have
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #12361 +/- ##
============================================
- Coverage 21.73% 21.64% -0.10%
- Complexity 9623 9654 +31
============================================
Files 268 268
Lines 36167 36244 +77
Branches 486 487 +1
============================================
- Hits 7862 7845 -17
- Misses 27823 27916 +93
- Partials 482 483 +1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
JManion32
left a comment
There was a problem hiding this comment.
This is a massive QOL improvement, I just have a few nitpicks (please push back if you feel otherwise):
Why change the <h1>? "My" is consistent with other pages:


In my opinion, we shouldn't use you at all here. From what I've seen, most of the site uses a documentation/"neutral" style of wording (a great example is the Manage Sections page) where we never explicitly reference the user.
Overall, I think this is a great change, but we should keep the paragraph/wording concise, and consistent with the rest of Submitty.
|
@JManion32 Thank you for the feedback, I changed the h1 because it was "My Late Day Usage" which also didn't match the title of the page and looked odd next to "You have X late days remaining". In my most recent commit I changed it to "My Late Days" and changed the h3 to also be neutral instead of 2nd person. I also made the other changes you suggested |
-Previously If statement would break page if late_days was not defined, changed the if statement to only affect h3 component
|
@cjreed121 Thank you for pointing that out. I moved the if statement so that only the h3 element is not rendered in the case where late_days is not defined. |
| } | ||
| } | ||
|
|
||
| .content > * + * { |
There was a problem hiding this comment.
This is quite a complicated selector. What are you trying to select? Can it be simpler?
There was a problem hiding this comment.
It just selects everything after the first element. If I just did ".content > * " it would add a top margin before "My Late Days" which isn't necessary and would make it inconsistent with every other page, so " * + * " selects everything after that for the top margin.
There was a problem hiding this comment.
This selector needs to be more specific. Please add a descriptive class to the particular element you're trying to style.
Rkoester47
left a comment
There was a problem hiding this comment.
I think these changes are intuitive and helpful for quickly seeing where you stand with late days. I believe updating the page header to match the title at the top is a good move for site consistency. After implementing requested changes, your code looks good and the feature is working properly for me.
JManion32
left a comment
There was a problem hiding this comment.
A few more wording changes:
- Always use
terminstead ofsemester, as not all schools use the semester system. - The first and last sentences seem redundant to me. What about something that combines them, like:
The table below provides a detailed history of your
late day balance throughout the term. Depending
on your course policy, you may have a fixed
amount, or the opportunity to earn additional days.
Other than that, this looks good, and will definitely improve the student experience. Great work!
JManion32
left a comment
There was a problem hiding this comment.
Wording / changes look good to me. This is a significant quality of life improvement for the Late Days page. Great work!
|
@cjreed121 do you approve the final version of this PR? |
| } | ||
| } | ||
|
|
||
| .content > * + * { |
There was a problem hiding this comment.
This selector needs to be more specific. Please add a descriptive class to the particular element you're trying to style.
williamjallen
left a comment
There was a problem hiding this comment.
Please also add a Cypress test as well.
|
|
||
| {% include 'LateDaysTablePlugin.twig' %} | ||
| </div> | ||
| </div> No newline at end of file |
There was a problem hiding this comment.
This whitespace change should be reverted.
There was a problem hiding this comment.
This still needs to be addressed.
| <h3> | ||
| Number of late days remaining: {{ late_days.getLateDaysRemaining() }} | ||
| </h3> | ||
| <p>The table below provides a detailed history of your | ||
| late day balance throughout the term. Depending | ||
| on your course policy, you may have a fixed | ||
| amount or the opportunity to earn additional days. | ||
| </p> |
There was a problem hiding this comment.
Can you please clean up the formatting here?
| <h3> | |
| Number of late days remaining: {{ late_days.getLateDaysRemaining() }} | |
| </h3> | |
| <p>The table below provides a detailed history of your | |
| late day balance throughout the term. Depending | |
| on your course policy, you may have a fixed | |
| amount or the opportunity to earn additional days. | |
| </p> | |
| <h3> | |
| Number of late days remaining: {{ late_days.getLateDaysRemaining() }} | |
| </h3> | |
| <p> | |
| The table below provides a detailed history of your | |
| late day balance throughout the term. Depending | |
| on your course policy, you may have a fixed | |
| amount or the opportunity to earn additional days. | |
| </p> |
Thank you for your review! Could you be a little more specific about what you had in mind for a Cypress test for this change? |
| } | ||
|
|
||
| .late-description{ | ||
| margin: 0.5rem, 0, 0.5rem, 0; |
There was a problem hiding this comment.
You can use margin: 0.5rem, 0; to be more concise. https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/margin
|
|
||
| {% include 'LateDaysTablePlugin.twig' %} | ||
| </div> | ||
| </div> No newline at end of file |
There was a problem hiding this comment.
This still needs to be addressed.
You should add a test which verifies that the correct number of late days remaining is displayed. The most difficult part will be figuring out how to manipulate the UI to result in 0, 1, and 2 late days remaining. |
Hi William, I made the text change you suggested and created an E2E test to show that the late day page updates when late days are given or removed from a student. Let me know if there is anything else this PR needs before it can be merged. |
Rkoester47
left a comment
There was a problem hiding this comment.
I checked the changes you've made and this branch still looks good to me. I ran the new cypress test locally, and it passed for me. I am approving this PR again.
Why is this Change Important & Necessary?
When Student users are looking for how many late days they currently have, they would either have to wait until an assignment was already past due to see how many late days they had or they could look at the "My Late Days" page, which had their current number of of late days at the very bottom right. For classes with many late-day additions, the relevant information to the user would be buried at the very bottom. This new change puts the relevant information to the user as the first thing they see.
What is the New Behavior?
Before:


After:
What steps should a reviewer take to reproduce or test the bug or new feature?
Automated Testing & Documentation
UI change, tests don't cover this change
Other information
This is an HTML change that talks to the HomeworkView API