Auto save

[gordon-cs]

Auto save

[superpowers11]

Hmm, I don't think adding the DamageId would require impossible amounts of magic. Can't you just return it on the AJAX response and then add it to the element?
So instead of having these two different states of damages in the UI (some in the db, some not), we just make the UI always reflect what is indeed in the db?

[superpowers11]

Can this be done by simply saving to db each time a description is entered, using an AJAX call? We were worried that would decrease performance and cause too many unnecessary db calls, especially if users decide to delete. But how often will a user delete a damage description they themselves just entered? And if it is an asynchronous call, the user should be able to continue their work even as the call to db is being made, no?

Isn't that supposed to be the beauty of AJAX? ✨

[eanyanwu]

We were worried that would decrease performance and cause too many unnecessary db calls, especially if users decide to delete.

I don't think that is the issue. If we make an AJAX call to add the damage to the db, the UI doesn't reflect that. The new damage still has the "new-damage" class insteady of being tagged with its DamageID (so it can be deleted later).
If we were to save on each damage addition, we would either:

• Need to refresh on each addition.....lolno
• Need to do some jquery magic to get the DamageID of the newly inserted component and give it an ID that reflects that.