Note: This is contingent on the base implementation being done or almost done.
The whole purpose of the user manager table is to quickly see every user in the database at a glance and update their attributes. The cleanest way for this (since mass editing likely won't be useful) is to display a modal whenever a user is clicked on with editable fields.
Work off of the branch role_manager_4.4.19
Action Items
Note: This is contingent on the base implementation being done or almost done.
The whole purpose of the user manager table is to quickly see every user in the database at a glance and update their attributes. The cleanest way for this (since mass editing likely won't be useful) is to display a modal whenever a user is clicked on with editable fields.
Work off of the branch
role_manager_4.4.19Action Items
userSelectedForEditexists in our state. If so, we should display the modal. I'd suggest creating a separate component likeEditUserModaland pass both thethis.onModalCloseanduserSelectedForEditas props. When the user isnull, the the modal should no longer be showing.Note: Don't hardcode the role and status options for the dropdowns. We already have these in a helper file! Check out
applicantInfoHelpers.jsand import the "roles" and "statuses." You can set the array of dropdown options toObject.values(roles)onModalClosecallback with the updated user from the form as a parameter. For "cancel," just callonModalClosewith no param to clear out theuserSelectedForEdit