jaeyun0503 commented on PR #4065: URL: https://github.com/apache/texera/pull/4065#issuecomment-3561498730
> I wonder whether you can do a simpler design: > > * Send the "Inactive -> Regular" change of User B to the backend to make the change persistent; > * (Optionally) Use Javascript to change the displayed status of User B to "Regular", just for this row. Or use a tooltip to show the change has been persistent. > > In this way, you don't need to fetch the entire list from the backend, and don't need to update other records either. My code is not involved with any part of the backend. This bug came from the frontend requesting a new user list from backend after editing (in `ngOnInit). I changed the code so that the code does NOT fetch from the backend again, but only changing the specific edited user in the frontend. No other record is updated. And to do the frontend change in place (the displayed status of the user's role you mentioned), I create a new User to replace the edited user in the userList and listOfDisplayUser arrays in the frontend. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
