-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Move a student to another class #16593
Conversation
247dadf
to
f56652d
Compare
@@ -217,6 +217,13 @@ final class StudentFormUi(helpers: Helpers, clasUi: ClasUi, studentUi: StudentUi | |||
cls := "button button-empty button-red", | |||
title := trans.clas.closeDesc1.txt() | |||
)(trans.clas.closeStudent()) | |||
), | |||
(!s.student.managed).option( |
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.
why this check?
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 coded the move for the managed student first and then I realized it was making sense for the non managed student too.
The views of managed and non managed students are a bit different.
When you click on a managed student in the list, you see 2 sets of actions
When you click on a non managed student you only have the first one
So I had a choice:
- Overloading the first set of actions with the move (keeping consistency between the 2 types of students)
- Do it one click later for the non managed in the edit form (but hiding it for the managed student because it was useless then)
So if you have a strong opinion about where it should be for this PR, I am happy to adapt.
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.
nice work, almost there
This PR starts addressing a concern expressed in this issue #16562
Before starting to search for the best solution to perform batch moves, there is a need for a 'move student' feature
Moving a student means:
UX:
I'm looking forward to your feedback