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

Mini Rubric: Keep Feedback When Switching Tabs #27507

Merged
merged 3 commits into from Mar 14, 2019
Merged

Conversation

dmcavoy
Copy link
Contributor

@dmcavoy dmcavoy commented Mar 13, 2019

We now don't unmount feedback tab when switching tabs. This allows us to keep all the state information with the Teacher Feedback Tab but also not lose unsaved feedback if a teacher wants to read the instructions in the middle of writing feedback.

Switch-Tabs-Keep-Feedback

Copy link
Contributor

@maddiedierker maddiedierker left a comment

Choose a reason for hiding this comment

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

clever way to keep the feedback component from unmounting!

@@ -237,8 +244,14 @@ class TeacherFeedback extends Component {

const rubricLevels = ['exceeds', 'meets', 'approaches', 'noEvidence'];

// Instead of unmounting the component when switching tabs hide and show it
// so a teacher does not lose the feedback they are giving if they switch tabs
const tabArea = this.props.visible
Copy link
Contributor

Choose a reason for hiding this comment

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

super nit: rename tabArea to something like tabVisible for clarity

Copy link
Member

@davidsbailey davidsbailey left a comment

Choose a reason for hiding this comment

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

This looks great, Dani! Thanks for taking the time to track down the best option before proceeding on this one.

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.

None yet

3 participants