32 · by Sharif Mehedi · in Developers · assigned to Sharif Mehedi

Résumé

Concepts sous-jacents

Commentaires

• 4 ans, 11 mois ago by Sharif Mehedi about #4118 (handling grid row(s) delete method & response) : fix check: route DOM properly after deleting a record
• 5 ans, 6 mois ago by Sharif Mehedi about #4118 (handling grid row(s) delete method & response) : I found the problem why after a delete react goes back to dashboard. It was because we were using, router.history.goBack() whereas it should be router.history.go(0) because the latest route known to router.history would be the route to LinoGrid.
• 5 ans, 6 mois ago by Luc Saffre about #4118 (handling grid row(s) delete method & response) : I merged your work and had a quick look at noi1r. The "Sort by" button is an interesting idea. The delete action is indeed a complex beast. Let's have another Jitsi session about it. Maybe today around 12:30 (UTC+3).
• 5 ans, 6 mois ago by Sharif Mehedi about #4118 (handling grid row(s) delete method & response) : I get your point. I start tracing the data flow on delete. Indeed there are multiple requests for user confirmation and all. I am reviewing the python side code now that handles the confirmed request. Afterwards I will checkout what happens to the response data and why react does not re-render datata...
• 5 ans, 6 mois ago by Luc Saffre about #4118 (handling grid row(s) delete method & response) : DELETE would be better, but the http method is just a convention. I seem to remeber tha delete and put are not supported as well as get and post in Django. Not sure whether this is still true. Another remark here is that clicking delete is not always a single ajax request. The server may ask for con...
• 5 ans, 6 mois ago by Sharif Mehedi about #4118 (handling grid row(s) delete method & response) : I wonder why the http method is GET when we are making a DELETE request!