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
Deeper learning: Remove deprecated UI #27407
Conversation
@@ -11,7 +11,6 @@ export default storybook => { | |||
name: 'Escalated Peer Review Submissions', |
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.
How are these stories different now, if both have the escalated status for all the submissions?
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 catch - they're not! I'll tear one out.
status: 'escalated', | ||
accepted_reviews: 1, | ||
rejected_reviews: 0 | ||
status: 'escalated' |
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.
How do we get in a state where the status
is 'escalated' but escalation_date
is undefined?
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'm not sure - this may not be a representative story. I'll review.
Two UI changes to the peer review dashboard. (PLC-67, spec)
Remove the "Escalated" and "Open" tabs.
Actually, remove the tabs entirely since we only care about the "All Submissions" view now. I've also removed this filter option from the API, since it's now unused.
Remove the "Accepted submissions" and "Rejected submissions" columns.
These columns aren't useful in the workflow this year and they take up quite a bit of space. I've also removed these counts from the summary data returned by the API.
Before:
After:
Done now, because it was fairly easy to do this cleanup while investigating and fixing a different Deeper Learning issue, in #27406.