You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now always the questionnaire edited will be send via POST to the server and writes into the database. Let's reduce those requests via comparing the saved questionnaire with the one in the browser before sending it off.
The text was updated successfully, but these errors were encountered:
That's one thing, but another is, that we now (2 minutes ago) got a new field called "updated_at", which always sets the date, when the model is saved. So if we always write to the database via the editor, we, even when not changing a thing, get a new date at "updated_at", which might be confusing to people at the survey_list page.
Yeah, mostly wondered on whether this should happen on the server or client. Doing it on the server seems easier/safer in general, but I also see advantages of doing it client side. And knowing whether to expect a new document in the client is useful.
Now always the questionnaire edited will be send via POST to the server and writes into the database. Let's reduce those requests via comparing the saved questionnaire with the one in the browser before sending it off.
The text was updated successfully, but these errors were encountered: