Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make autosave optional #25

Open
sweh opened this issue Dec 4, 2015 · 2 comments
Open

Make autosave optional #25

sweh opened this issue Dec 4, 2015 · 2 comments

Comments

@sweh
Copy link
Owner

sweh commented Dec 4, 2015

Originally reported by: Florian Pilz (Bitbucket: florianpilz, GitHub: florianpilz)


Currently the form always uses autosave, thus you must adjust your model to not contain required fields to use gocept.jsform. This is not very programmer-friendly. We should also allow to disable autosave, thus a save button is used to submit the form.

The approach to use no autosave is very helpful when all options and values are given up front, rather relying on a JSON API on server side. Maybe we should render the save button automatically when autosave is disabled.


@florianpilz
Copy link
Contributor

👍 By default we should not use auto-saving, since most programmers are unfamiliar with this approach, hence making it more difficult to get started with the library. Besides, the real value of auto-saving must be build into the App from ground up, e.g. should notify the user of "drafts" in case of incomplete forms etc.

@florianpilz
Copy link
Contributor

We should really push this enhancement forward. One of our clients had issues, since they are accustomed to the "save on send" approach. Also, we were not able to "quickly" show how this can be changed. I know it's possible, but it is not easy and you still need to avoid required fields in the model due to auto-validation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants