bouvyd’s avatarbouvyd’s Twitter Archive—№ 1,852

    1. …in reply to @Dolmayan62
      @Dolmayan62 @Yenthe666 No, there is no field autosave, nor is there a time-delayed autosave. We save: - when the user manually saves with the button - when the user runs an action via the UI (e.g. buttons that call code, server actions or window actions) - when the user navigates away (e.g. breadcrumb)
  1. …in reply to @bouvyd
    @Dolmayan62 @Yenthe666 The rationale behind not having a 'field by field' autosave were that: - this would have a big impact on server load - in case of constraints, it might not be able to save - changing a field with computes/on changes can lead to other changes, that the user may want to discard